konserve-s3.core — org.replikativ/konserve-s3 0.1.30

S3 based konserve backend.

->key clj

(->key store-id key)

bucket-exists? clj

(bucket-exists? client bucket)

common-client-config clj

(common-client-config client
                      {:keys [region x-ray? access-key secret endpoint-override
                              path-style-access? expect-continue?]})

connect-store clj

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

copy clj

(copy client bucket source-key destination-key)

create-bucket clj

(create-bucket client bucket)

default-bucket clj

delete clj

(delete client bucket key)

delete-bucket clj

(delete-bucket client bucket)

delete-keys clj

(delete-keys client bucket keys)

delete-store clj

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

deletion-batch-size clj

exists? clj

(exists? client bucket key)

get-object clj

(get-object client bucket key)

get-object-with-etag clj

(get-object-with-etag client bucket key)

Get object and return map with :data and :etag, or nil if not found.

list-objects clj

(list-objects client bucket)

list-stores clj

(list-stores s3-spec & {:keys [opts]})

List all konserve stores in an S3 bucket by reading the central registry.

The registry uses optimistic concurrency control (ETags) to handle concurrent updates from multiple processes/machines.

Args: s3-spec - Map with :bucket, :region, :access-key, :secret, etc. opts - (optional) Runtime options map. Defaults to {:sync? true}

Returns: Set of UUIDs representing store IDs in the bucket

output-stream-buffer-size clj

put-object clj

(put-object client bucket key bytes)

put-object-conditional clj

(put-object-conditional client bucket key bytes if-match-etag)

Put object with conditional ETag check. Returns true on success, false on conflict. S3 returns HTTP 412 (Precondition Failed) when ifMatch ETag doesn't match.

regions clj

release clj

(release store env)

Must be called after work on database has finished in order to close connection

s3-client clj

(s3-client opts)

strip-expect-continue-interceptor clj

The SDK forces Expect: 100-continue onto PutObject via an internal interceptor regardless of HTTP-client configuration (aws/aws-sdk-java-v2 #6537). The handshake costs a full extra round trip per PUT — and stalls against providers that never send the interim 100 response (Cloudflare R2). It only pays off for uploads large enough that resending a rejected body hurts, which konserve values are not. Override-config interceptors run after the SDK's own, so removing the header here wins.