Skip to content

Dynamodb support - #812

Merged
flarco merged 2 commits into
v1.6.4from
flarco/dynamodb-support
Sep 22, 2026
Merged

flarco merged 2 commits into
v1.6.4from
flarco/dynamodb-support

Conversation

@flarco

@flarco flarco commented Sep 22, 2026

Copy link
Copy Markdown
Collaborator

No description provided.

- DynamoDB has no SQL engine, so reads become paginated Scans driven by a
  JSON scan descriptor (filter/fields/limit) and writes become
  BatchWriteItem puts that upsert by primary key.
- Tables cannot exist without a key: `primary_key` and unique keys are
  honored, and a `_sling_id` column is added when a stream declares none,
  so repeated data values cannot collapse rows on write.
- delete_missing soft/hard are supported by parsing the rendered
  update/delete statements and resolving the `not exists` join against the
  stream's temp keys, keeping rows the stream still holds.
- Credentials come from the AWS credential chain, region from the URL host
  or env, and a custom `endpoint` supports DynamoDB Local.
- Registered in type, template, URL and direct-write plumbing, with unit
  tests, a CLI suite entry and an end-to-end pipeline.
@flarco
flarco merged commit ff86770 into v1.6.4 Sep 22, 2026
1 check passed
@flarco
flarco deleted the flarco/dynamodb-support branch September 29, 2026 21:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant