HTTP
Crux offers a REST API layer in the crux-http-server
module that allows you to send transactions and run queries over HTTP.
Using Crux in this manner is a valid use-case but it cannot support all of the features and benefits that running the Crux node inside of your application provides, in particular the ability to efficiently combine custom code with multiple in-process Datalog queries.
Your application only needs to communicate with one Crux node when using the REST API. Multiple Crux nodes can placed be behind a HTTP load balancer to spread the writes and reads over a horizontally-scaled cluster transparently to the application. Each Crux node in such a cluster will be independently catching up with the head of the transaction log, and since different queries might go to different nodes, you have to be slightly conscious of read consistency when designing your application to use Crux in this way. Fortunately, you can readily achieve read-your-writes consistency with the ability to query consistent point-in-time snapshots using specific temporal coordinates.
The REST API also provides an experimental endpoint for SPARQL 1.1 Protocol queries under /_crux/sparql/
, rewriting the query into the Crux Datalog dialect.
Only a small subset of SPARQL is supported and no other RDF features are available.
Starting an HTTP Server
Project Dependency
pro.juxt.crux/crux-http-server {:mvn/version "1.17.1"}
You can start up a Jetty HTTP/HTTP2 server on a node by including crux.http-server/server
in your node configuration, optionally passing the server port:
Parameters
-
port
(int, default 3000) -
read-only?
(boolean, default false): start the HTTP server in read-only mode -
jwks
(string): JSON Web Token (JWT) key set to authorise requests against -{"keys": […]}
-
jetty-opts
(map): further options to pass to the Ring Jetty adapter
Ring Handler
Crux also exposes a Ring handler that you can include within your own Ring-compatible server, with parameters as above:
(crux.http-server/->crux-handler crux-node {...})
Using a Remote API Client
In addition to calling the HTTP endpoints directly you can also use the remote API client, which implements the same interfaces/protocols as a local Crux node, where possible.
Project Dependency
pro.juxt.crux/crux-http-client {:mvn/version "1.17.1"}
To connect to a pre-existing remote node, you need a URL to the node and the above on your classpath.
We can then call crux.api/new-api-client
, passing the URL.
If the node was started on localhost:3000
, you can connect to it by doing the following:
(defn start-http-client [port]
(crux/new-api-client (str "http://localhost:" port)))
Using the REST API
All of the REST endpoints return application/edn
, application/json
and application/transit+json
.
Individual endpoints may return additional types - see their docs below, or see the
OpenAPI documentation here.
All endpoints with query-parameters accept them in both a kebab-case and camel cased format, (ie: if valid-time is taken, validTime will also be taken)
|
GET /_crux/status
Returns the current status information of the node.
Response
{
"version": "1.17.1",
"revision": null,
"indexVersion": 13,
"consumerState": null,
"kvStore": "crux.rocksdb.RocksKv",
"estimateNumKeys": 3,
"size": 1326658
}
{:crux.version/version "1.17.1",
:crux.version/revision nil, :crux.index/index-version 13,
:crux.doc-log/consumer-state nil,
:crux.tx-log/consumer-state nil,
:crux.kv/kv-store "crux.rocksdb.RocksKv",
:crux.kv/estimate-num-keys 3,
:crux.kv/size 132665
GET /_crux/entity
Returns the document map for a particular entity.
Query Parameters
-
One of the following:
-
eid-edn
(EDN formatted Crux ID) -
eid-json
(JSON formatted Crux ID) -
eid
(String IDs)
-
-
valid-time
(date, defaulting to now) -
tx-time
(date, defaulting to latest transaction time) -
tx-id
(date, defaulting to latest transaction id)
GET /_crux/entity?history=true
Returns the history of a particular entity.
Query Parameters
-
One of the following:
-
eid-edn
(EDN formatted Crux ID) -
eid-json
(JSON formatted Crux ID) -
eid
(String IDs)
-
-
sort-order
(eitherasc
ordesc
)
-
with-corrections
(boolean, default false): includes bitemporal corrections in the response, inline, sorted by valid-time then tx-id -
with-docs
(boolean, default false): includes the documents in the response sequence, under thedoc
key -
start-valid-time
,start-tx-time
,start-tx-id
(inclusive, default unbounded): bitemporal co-ordinates to start at -
end-valid-time
,end-tx-time
,end-tx-id
(exclusive, default unbounded): bitemporal co-ordinates to stop at
Response
[
{
"txTime": "2020-10-16T14:24:17Z",
"txId": 3,
"validTime": "2020-10-16T14:24:17Z",
"contentHash": "99747f80357c336ee5efd073c878313bf85b07f9"
},
{
"txTime": "2020-10-16T14:29:31Z",
"txId": 4,
"validTime": "2020-10-16T14:29:31Z",
"contentHash": "88d61c8de82eda2a53784bb0438e1a751cd68f96"
},
{
"txTime": "2020-10-16T14:29:35Z",
"txId": 5,
"validTime": "2020-10-16T14:29:35Z",
"contentHash": "99747f80357c336ee5efd073c878313bf85b07f9"
}
]
({:crux.tx/tx-time #inst "2020-10-16T14:24:17.025-00:00",
:crux.tx/tx-id 3,
:crux.db/valid-time #inst "2020-10-16T14:24:17.025-00:00",
:crux.db/content-hash #crux/id "99747f80357c336ee5efd073c878313bf85b07f9"}
{:crux.tx/tx-time #inst "2020-10-16T14:29:31.928-00:00",
:crux.tx/tx-id 4,
:crux.db/valid-time #inst "2020-10-16T14:29:31.928-00:00",
:crux.db/content-hash #crux/id "88d61c8de82eda2a53784bb0438e1a751cd68f96"}
{:crux.tx/tx-time #inst "2020-10-16T14:29:35.664-00:00",
:crux.tx/tx-id 5,
:crux.db/valid-time #inst "2020-10-16T14:29:35.664-00:00",
:crux.db/content-hash #crux/id "99747f80357c336ee5efd073c878313bf85b07f9"})
GET /_crux/entity-tx
Returns the transaction details for an entity - returns a map containing the tx-id and tx-time.
Query Parameters
-
One of the following:
-
eid-edn
(EDN formatted Crux ID) -
eid-json
(JSON formatted Crux ID) -
eid
(String IDs)
-
-
valid-time
(date, defaulting to now) -
tx-time
(date, defaulting to latest transaction time) -
tx-id
(date, defaulting to latest transaction id)
Response
{
"id": "5aeebab117b892fa42002146e4c62be676bc4621",
"contentHash": "99747f80357c336ee5efd073c878313bf85b07f9",
"validTime": "2020-10-16T14:29:35Z",
"txTime": "2020-10-16T14:29:35Z",
"txId": 5
}
{:crux.db/id #crux/id "5aeebab117b892fa42002146e4c62be676bc4621",
:crux.db/content-hash #crux/id "99747f80357c336ee5efd073c878313bf85b07f9",
:crux.db/valid-time #inst "2020-10-16T14:29:35.664-00:00",
:crux.tx/tx-time #inst "2020-10-16T14:29:35.664-00:00",
:crux.tx/tx-id 5}
GET /_crux/query
Takes a datalog query and returns its results. Results are also available in text/csv
and text/tsv
formats (can force negotiation of these by using the /_crux/query.csv
and /_crux/query.tsv
endpoints respectively).
Query Parameters
-
query-edn
(URL encoded datalog query)
-
valid-time
(date, defaulting to now) -
tx-time
(date, defaulting to latest transaction time) -
tx-id
(date, defaulting to latest transaction id) -
in-args-edn
(EDN URL encoded :in binding arguments) -
in-args-json
(JSON URL encoded :in binding arguments)
POST /_crux/query
Takes a datalog query and returns its results. Results are also available in text/csv
and text/tsv
formats (can force negotiation of these by using the /_crux/query.csv
and /_crux/query.tsv
endpoints respectively).
Request
curl -g \
-X POST \
-H "Accept: application/edn" \
-H "Content-Type: application/edn" \
-d '{:query {:find [e first-name] :where [[e :first-name first-name] [e :last-name "Tutorial"]]}}' \
$CRUX_URL/_crux/query
You can also accept application/json from this endpoint, but currently the only supported Content-Type for posting queries is application/edn .
|
GET /_crux/sync
Wait until the Kafka consumer’s lag is back to 0 (i.e. when it no longer has pending transactions to write). Returns the transaction time of the most recent transaction.
GET /_crux/await-tx
Waits until the node has indexed a transaction that is at or past the supplied tx-id. Returns the most recent tx indexed by the node.
GET /_crux/await-tx-time
Blocks until the node has indexed a transaction that is past the supplied tx-time. The returned date is the latest index time when this node has caught up as of this call.
GET /_crux/tx-log
Returns a list of all transactions, from oldest to newest transaction time - optionally including documents.
Query Parameters
-
after-tx-id
(integer, default unbounded): transaction id to start after. -
with-ops?
(boolean, defaults to false): should the operations with documents be included?
Response
[
{
"txId": 0,
"txTime": "2020-10-16T09:02:43Z",
"txEvents": [
[
"put",
"83bed47ace572cb94c2f137f58bce73b9b7d0039",
"f441402b3c5d37365203947aabe85cf471498bf0",
"2020-06-20T20:05:50Z"
]
]
},
{
"txId": 1,
"txTime": "2020-10-16T09:28:27Z",
"txEvents": [
[
"put",
"83bed47ace572cb94c2f137f58bce73b9b7d0039",
"f441402b3c5d37365203947aabe85cf471498bf0",
"2020-06-20T20:05:50Z"
]
]
}
]
({:crux.tx/tx-id 0,
:crux.tx/tx-time #inst "2020-10-16T09:02:43.429-00:00",
:crux.tx.event/tx-events [[:crux.tx/put
#crux/id "83bed47ace572cb94c2f137f58bce73b9b7d0039"
#crux/id "f441402b3c5d37365203947aabe85cf471498bf0"
#inst "2020-06-20T20:05:50.000-00:00"]]}
{:crux.tx/tx-id 1,
:crux.tx/tx-time #inst "2020-10-16T09:28:27.785-00:00",
:crux.tx.event/tx-events [[:crux.tx/put
#crux/id "83bed47ace572cb94c2f137f58bce73b9b7d0039"
#crux/id "f441402b3c5d37365203947aabe85cf471498bf0"
#inst "2020-06-20T20:05:50.000-00:00"]]})
POST /_crux/submit-tx
Takes a vector of transactions (any combination of put
, delete
, match
, evict
and fn
) and executes them in order. This is the only "write" endpoint.
Request
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"tx-ops": [["put", {"crux.db/id": "ivan", "name": "Ivan", "last-name": "Petrov"}],
["put", {"crux.db/id": "boris", "name": "Boris", "last-name": "Petrov"}],
["delete", "maria", "2012-05-07T14:57:08.462-00:00"]]}' \
$CRUX_URL/_crux/submit-tx
Note: Transaction functions should be submitted as strings containing clojure code, and read in as EDN.
curl -X POST \
-H "Content-Type: application/edn" \
-H "Accept: application/edn" \
-d '{:tx-ops [[:crux.tx/put {:crux.db/id :ivan, :name "Ivan" :last-name "Petrov"}],
[:crux.tx/put {:crux.db/id :boris, :name "Boris" :last-name "Petrov"}],
[:crux.tx/delete :maria #inst "2012-05-07T14:57:08.462-00:00"]]}' \
$CRUX_URL/_crux/submit-tx
GET /_crux/tx-committed
Checks if a submitted tx was successfully committed, returning a map with tx-committed and either true
or false
(or a NodeOutOfSyncException
exception response if the node has not yet indexed the transaction).
GET /_crux/latest-completed-tx
Returns the latest transaction to have been indexed by this node.
GET /_crux/latest-submitted-tx
Returns the latest transaction to have been submitted to this cluster.
GET /_crux/active-queries
Returns a list of currently running queries.
Response
[
{
"status": "in-progress",
"queryId": "ae17c599-dcd2-47ee-bebd-47a3122f8d34",
"query": "{:find [e first-name], :where [[e :first-name first-name] [e :last-name \"Tutorial\"]]}",
"startedAt": "2020-10-16T15:48:52Z",
"finishedAt": null,
"error": null
}
]
({:status :in-progress
:query-id "ae17c599-dcd2-47ee-bebd-47a3122f8d34",
:query {:find [e first-name], :where [[e :first-name first-name] [e :last-name "Tutorial"]]},
:started-at #inst "2020-10-16T15:48:52.656-00:00",
:finished-at nil
:error nil})
GET /_crux/recent-queries
Returns a list of recently completed/failed queries.
Response
[
{
"status": "completed",
"queryId": "ae17c599-dcd2-47ee-bebd-47a3122f8d34",
"query": "{:find [e first-name], :where [[e :first-name first-name] [e :last-name \"Tutorial\"]]}",
"startedAt": "2020-10-16T15:48:52Z",
"finishedAt": "2020-10-16T15:48:52Z",
"error": null
}
]
({:status :completed,
:query-id "ae17c599-dcd2-47ee-bebd-47a3122f8d34",
:query {:find [e first-name], :where [[e :first-name first-name] [e :last-name "Tutorial"]]},
:started-at #inst "2020-10-16T15:48:52.656-00:00",
:finished-at #inst "2020-10-16T15:48:52.835-00:00",
:error nil})
GET /_crux/slowest-queries
Returns a list of slowest completed/failed queries ran on the node.
Response
[
{
"status": "completed",
"queryId": "ae17c599-dcd2-47ee-bebd-47a3122f8d34",
"query": "{:find [e first-name], :where [[e :first-name first-name] [e :last-name \"Tutorial\"]]}",
"startedAt": "2020-10-16T15:48:52Z",
"finishedAt": "2020-10-16T15:48:52Z",
"error": null
}
]
({:status :completed,
:query-id "ae17c599-dcd2-47ee-bebd-47a3122f8d34",
:query {:find [e first-name], :where [[e :first-name first-name] [e :last-name "Tutorial"]]},
:started-at #inst "2020-10-16T15:48:52.656-00:00",
:finished-at #inst "2020-10-16T15:48:52.835-00:00",
:error nil})