konserve-dynamodb.core — org.replikativ/konserve-dynamodb 0.1.34

DynamoDB based konserve backend.

batch-get-items clj

(batch-get-items client table-name store-keys consistent-read?)

Fetch up to 100 distinct keys, retrying partial responses with bounded backoff. Returns an aggregated BatchGetItemResponse. Exhaustion throws rather than presenting unprocessed keys as missing.

batch-write-fragments! clj

(batch-write-fragments! client table items)

Stage at most 25 immutable 300 KiB fragments. Even with base64 and envelope overhead this stays below BatchWriteItem's 16 MiB wire limit. Retry only UnprocessedItems; callers must not publish manifests until this succeeds.

connect-store clj

(connect-store dynamodb-spec & {:keys [opts] :as params})

create-dynamodb-table clj

(create-dynamodb-table client table-name {:keys [read-capacity write-capacity]})

delete-dynamodb-table clj

(delete-dynamodb-table client table-name)

delete-item clj

(delete-item client table-name key)

delete-store clj

(delete-store dynamodb-spec & {:keys [opts]})

dynamodb-client clj

(dynamodb-client opts)

Creates a new DynamoDB client using the provided options, with explicit credential handling.

get-item clj

(get-item client table-name key consistent-read?)

put-item clj

(put-item client table-name item)

put-item-conditional clj

(put-item-conditional client table-name item expected-meta)

PutItem only if the stored Meta attribute is still expected-meta — or, when that is ::absent, only if the item does not exist. True on success, false when DynamoDB refuses.

DynamoDB evaluates the condition itself, atomically with the write, which is what makes this backing's guarantee :global: it holds against every writer anywhere, not merely those sharing a filesystem or a heap.

The condition compares the META attribute rather than a separate version column. konserve's revision lives inside the serialized metadata, so the meta bytes ARE the revision as far as this item is concerned — and comparing them needs no schema change, no second attribute to keep in step, and no migration for existing tables. Meta is small; the value is not compared and not sent.

Expression attribute NAMES for both Key and Meta: KEY is a DynamoDB reserved word, and a literal in an expression would be rejected.

release clj

(release store env)

Release the store connection.

scan-table clj

(scan-table client table-name)

(scan-table client table-name start-key)

(scan-table client table-name start-key consistent-read?)

store-exists? clj

(store-exists? dynamodb-spec & {:keys [opts]})

table-exists? clj

(table-exists? client table-name)

transact-write-items clj

(transact-write-items client transact-items)

Execute multiple write operations in a single, atomic transaction. Limited to 100 items per transaction by DynamoDB.