Difference between revisions of " Nano Sparql Server"

From Blazegraph
Jump to: navigation, search
Line 1: Line 1:
 
= Running the embedded NanoSparqlServer =
 
= Running the embedded NanoSparqlServer =
 +
 +
TBD
 +
 
= Deploying a SPARQL servlet endpoint =
 
= Deploying a SPARQL servlet endpoint =
 +
 +
TBD
 +
 
= HTTP METHODS =
 
= HTTP METHODS =
 +
 
== Query ==
 
== Query ==
 +
 
=== GET or POST ===
 
=== GET or POST ===
 
<pre>
 
<pre>
Line 12: Line 20:
 
</pre>
 
</pre>
  
The response body is the result of the query.
+
The response body is the result of the query. The following query parameters are understood:
 +
 
 +
{| class="wikitable"
 +
|-
 +
! parameter
 +
! definition
 +
|-
 +
| timestamp
 +
| A timestamp corresponding to a commit time against which the query will read.
 +
|}
  
 
== Update ==
 
== Update ==
Line 66: Line 83:
 
Various information about the SPARQL end point.  Options include:
 
Various information about the SPARQL end point.  Options include:
  
<pre>
+
 
?showQueries=true|false
+
{| class="wikitable"
?showRunningQueries=true|false
+
|-
?showNamespaces=true|false
+
! parameter
?showKBInfo=true|false
+
! definition
</pre>
+
|-
 +
| showQueries
 +
| Show SPARQL queries accepted by the HTTP end point.
 +
|-
 +
| showRunningQueries
 +
| Show the internal IRunningQuery object for queries which are currently executing.
 +
|-
 +
| showNamespaces
 +
| Show a list of namespaces of triple or quad store instances in the bigdata database.
 +
|-
 +
| showKBInfo
 +
| Show some low level details about the backend database.
 +
|}

Revision as of 17:02, 7 April 2011

Running the embedded NanoSparqlServer

TBD

Deploying a SPARQL servlet endpoint

TBD

HTTP METHODS

Query

GET or POST

GET [/namespace/NAMESPACE] ?query=...

-OR-

POST [/namespace/NAMESPACE] ?query=...

The response body is the result of the query. The following query parameters are understood:

parameter definition
timestamp A timestamp corresponding to a commit time against which the query will read.

Update

POST with Body

POST [/namespace/NAMESPACE]
...
Content-Type: 
...
BODY

Perform an HTTP-POST, which corresponds to the basic CRUD operation "create" according to the generic interaction semantics of HTTP REST. The operation will be executed against the target namespace per the URI.

Where BODY is the new RDF content using the representation indicated by the Content-Type.

POST with URLs (upload)

POST [/namespace/NAMESPACE] ?uri=URI

Where URI identifies a resource whose RDF content will be inserted into the database. The uri query parameter may occur multiple times. All identified resources will be loaded within a single native transaction. Bigdata provides snapshot isolation so you can continue to execute queries against the last commit point while this operation is executed.

DELETE with Query

DELETE [/namespace/NAMESPACE] ?query=...

Where query is a CONSTRUCT or DESCRIBE query. Statements are materialized using the query from the addressed namespace are deleted from that namespace.

Note: To avoid materializing the statements, this runs the query against the last commit time. This is done while it is holding the unisolated connection which prevents concurrent modifications. Therefore the entire QUERY + DELETE operation is ACID.

DELETE with Body

POST [/namespace/NAMESPACE]
 ...
Content-Type
 ...

BODY

BODY contains RDF statements according to the specified Content-Type. Statements parsed from the BODY are deleted from the addressed namespace.

Status

GET /status

Various information about the SPARQL end point. Options include:


parameter definition
showQueries Show SPARQL queries accepted by the HTTP end point.
showRunningQueries Show the internal IRunningQuery object for queries which are currently executing.
showNamespaces Show a list of namespaces of triple or quad store instances in the bigdata database.
showKBInfo Show some low level details about the backend database.