Nano Sparql Server
Running the embedded NanoSparqlServer
Deploying a SPARQL servlet endpoint
GET or POST
GET [/namespace/NAMESPACE] ?query=... -OR- POST [/namespace/NAMESPACE] ?query=...
The response body is the result of the query.
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.
Various information about the SPARQL end point. Options include:
?showQueries=true|false ?showRunningQueries=true|false ?showNamespaces=true|false ?showKBInfo=true|false