mapbox / mapbox/dynamodb-replicator
Replicate to a table with a different key schema
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 131
- Forks
- 46
- PR merge metrics
- No merged PRs in 30d
Description
A bit of an unusual use case but in trying to replicate to destination table with an different key schema than the source table, [this line](https://github.com/mapbox/dynamodb-replicator/blob/0674417be8bcbd7ceed2b6e5e2b2d1d4a30eaf1a/index.js#L108) is problematic. We are assuming both tables have identical key schema.
We could workaround this by allowing the user to define the destination key schema explicitly or by looking up the key schema for the destination table.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at index.js line 108, where replication assumes the source and destination tables have identical key schemas. Determine whether destination keys should be explicitly configured or looked up, then verify that replication supports differing schemas without relying on the source schema.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100