Liking cljdoc? Tell your friends :D

(ns crux.api)

ICruxSystem

db

  (db
    [system]
    [system ^Date valid-time]
    [system ^Date valid-time ^Date transaction-time]
    "Will return the latest value of the db currently known. Non-blocking.

     When a valid time is specified then returned db value contains only those
     documents whose valid time is not after the specified. Non-blocking.

     When both valid and transaction time are specified returns a db value
     as of the valid and transaction time. Will block until the transaction
     time is present in the index.")

document

  (document [system content-hash]
    "Reads a document from the document store based on its
    content hash.")

history

  (history [system eid]
    "Returns the transaction history of an entity, in reverse
    chronological order. Includes corrections, but does not include
    the actual documents.")

history-range

  (history-range [system eid
                  ^Date valid-time-start
                  ^Date transaction-time-start
                  ^Date valid-time-end
                  ^Date transaction-time-end]
    "Returns the transaction history of an entity, ordered by valid
    time / transaction time in chronological order, earliest
    first. Includes corrections, but does not include the actual
    documents.

    Giving null as any of the date arguments makes the range open
    ended for that value.")

status

  (status [system]
    "Returns the status of this node as a map.")

submit-tx

  (submit-tx [system tx-ops]
    "Writes transactions to the log for processing
     tx-ops datalog style transactions.
     Returns a map with details about the submitted transaction,
     including tx-time and tx-id.")

submitted-tx-updated-entity?

  (submitted-tx-updated-entity? [system submitted-tx eid]
    "Checks if a submitted tx did update an entity.
    submitted-tx must be a map returned from `submit-tx`
    eid is an object that can be coerced into an entity id.
    Returns true if the entity was updated in this transaction.")

submitted-tx-corrected-entity?

  (submitted-tx-corrected-entity? [system submitted-tx ^Date valid-time eid]
    "Checks if a submitted tx did correct an entity as of valid time.
    submitted-tx must be a map returned from `submit-tx`
    valid-time valid time of the correction to check.
    eid is an object that can be coerced into an entity id.
    Returns true if the entity was updated in this transaction.")

sync

  (sync [system ^Duration timeout]
    "Blocks until the node has caught up indexing. Will throw an
    exception on timeout. The returned date is the latest index
    time when this node has caught up as of this call. This can be
    used as the second parameter in (db valid-time, transaction-time)
    for consistent reads.

    timeout – max time to wait, can be null for the default.
    Returns the latest known transaction time.")

new-tx-log-context

  (new-tx-log-context ^java.io.Closeable [system]
    "Returns a new transaction log context allowing for lazy reading
    of the transaction log in a try-with-resources block using
    (tx-log ^Closeable tx-Log-context, from-tx-id, boolean with-documents?).

    Returns an implementation specific context.")

tx-log

  (tx-log [system tx-log-context from-tx-id with-documents?]
    "Reads the transaction log lazily. Optionally includes
    documents, which allow the contents under the :crux.tx/tx-ops
    key to be piped into (submit-tx tx-ops) of another
    Crux instance.
    tx-log-context  a context from (new-tx-log-context system)
    from-tx-id      optional transaction id to start from.
    with-documents? should the documents be included?

    Returns a lazy sequence of the transaction log."))

ICruxDatasource

Represents the database as of a specific valid and transaction time.

entity

  (entity [db eid]
    "queries a document map for an entity.
    eid is an object which can be coerced into an entity id.
    returns the entity document map.")

entity-tx

  (entity-tx [db eid]
    "returns the transaction details for an entity. Details
    include tx-id and tx-time.
    eid is an object that can be coerced into an entity id.")

new-snapshot

  (new-snapshot ^java.io.Closeable [db]
     "Returns a new implementation specific snapshot allowing for lazy query results in a
     try-with-resources block using (q db  snapshot  query)}.
     Can also be used for
     (history-ascending db snapshot  eid) and
     (history-descending db snapshot  eid)
     returns an implementation specific snapshot")

q

  (q
    [db query]
    [db snapshot query]
    "q[uery] a Crux db.
    query param is a datalog query in map, vector or string form.
    First signature will evaluate eagerly and will return a set or vector
    of result tuples.
    Second signature accepts a db snapshot, see `new-snapshot`.
    Evaluates *lazily* consequently returns lazy sequence of result tuples.")

history-ascending

  (history-ascending
    [db snapshot eid]
    "Retrieves entity history lazily in chronological order
    from and including the valid time of the db while respecting
    transaction time. Includes the documents.")

history-descending

  (history-descending
    [db snapshot eid]
    "Retrieves entity history lazily in reverse chronological order
    from and including the valid time of the db while respecting
    transaction time. Includes the documents.")

valid-time

  (valid-time [db]
    "returns the valid time of the db.
    If valid time wasn't specified at the moment of the db value retrieval
    then valid time will be time of the latest transaction.")

transaction-time

  (transaction-time [db]
    "returns the time of the latest transaction applied to this db value.
    If a tx time was specified when db value was acquired then returns
    the specified time."))

Lifecycle members

start-cluster-node

(defn start-cluster-node ^ICruxAPI [options])

Starts a query node in local library mode.

For valid options, see crux.bootstrap/cli-options. Options are specified as keywords using their long format name, like :bootstrap-servers etc.

requires any KV store dependencies and kafka-clients on the classpath. The crux.kv.memdb.MemKv KV backend works without additional dependencies.

The HTTP API can be started by passing the system to crux.http-server/start-http-server. This will require further dependencies on the classpath, see crux.http-server for details.

Options:

{:kv-backend        "crux.kv.rocksdb.RocksKv" ; requires RocksDB as dep
                    "crux.kv.memdb.MemKv" ; will work without addional deps
:bootstrap-servers  "kafka-cluster-kafka-brokers.crux.svc.cluster.local:9092"
:event-log-dir      "data/eventlog-1"
:db-dir             "data/db-dir-1"
:backup-dir         "checkpoint"
:group-id           "group-id"
:tx-topic           "crux-transaction-log"
:doc-topic          "crux-docs"
:create-topics      true
:doc-partitions     1
:replication-factor 1
:db-dir             "data"
:server-port        3000
:await-tx-timeout   10000
:doc-cache-size     131072
:object-store       "crux.index.KvObjectStore"}

Returns the started local node that implements ICruxAPI and java.io.Closeable. Latter allows the system to be stopped by calling (.close node).

Throws IndexVersionOutOfSyncException if the index needs rebuilding.

start-standalone-system

(defn start-standalone-system ^ICruxAPI [options])

Creates a minimal standalone system writing the transaction log into its local KV store without relying on Kafka. Alternatively, when the event-log-dir option is provided, using two KV stores to enable rebuilding the index from the event log, being more similar to the semantics of Kafka but for a single process only.

requires any KV store dependencies on the classpath. The crux.kv.memdb.MemKv KV backend works without additional dependencies.

Options:

{:kv-backend    "crux.kv.rocksdb.RocksKv" ; or crux.kv.memdb.MemKv
 :event-log-dir "data/eventlog-1"
 :db-dir        "data/db-dir-1"
 :backup-dir    "checkpoint"}

See start-cluster-node doc for more options

Returns a standalone system which implements ICruxAPI and java.io.Closeable. Latter allows the system to be stopped by calling (.close node).

Throws IndexVersionOutOfSyncException if the index needs rebuilding.

Throws NonMonotonicTimeException if the clock has moved backwards since last run. Only applicable when using the event log.

new-api-client

(defn new-api-client ^ICruxAPI [url])

Creates a new remote API client ICruxAPI. The remote client requires valid and transaction time to be specified for all calls to db.

requires either clj-http or http-kit on the classpath, see crux.bootstrap.remove-api-client/internal-http-request-fn for more information.

Param url the URL to a Crux HTTP end-point.

Returns a remote API client.

Can you improve this documentation?Edit on GitHub

cljdoc is a website building & hosting documentation for Clojure/Script libraries

× close