incremental-snapshot creates extra output in snapshot
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 42/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- aws, javascript
Research direction
Start with bin/incremental-snapshot.js and reproduce the snapshot command against the S3 paths shown in the issue. Inspect the decompressed output for blank lines and trace how records are written; done means incremental snapshots contain no unintended empty lines.
Written by the indexing model from the issue text.
Description
bin/incremental-snapshot.js s3://$BackupBucket/$BackupPrefix/$TABLE s3://$BackupBucket/${TABLE}-snapshot
sometimes this leaves empty lines in the snapshot output - for example:
aws s3 cp s3://$BackupBucket/${TABLE}-snapshot - | gzcat
{"what":{"S":"new1"},"a":{"S":"b"}}
{"what":{"S":"new2"},"a":{"S":"11"}}
{"what":{"S":"a"},"b":{"S":"ccd"}}
{"what":{"S":"test2"},"a":{"S":"asdf"}}
{"what":{"S":"new10"},"a":{"S":"b"}}
{"what":{"S":"sdfg"},"a":{"S":"asdf"}}
{"what":{"S":"asdf"},"aa":{"S":"bb"}}
{"what":{"S":"test"},"a":{"S":"test1"}}
{"what":{"S":"new"},"a":{"S":"fish faster 8"}}
{"what":{"S":"test4"}}
{"what":{"S":"b"},"a":{"S":"aa"},"b":{"S":"cc"}}
This one, anyway, is easy enough to handle during the uncompress ( | gzip | grep -v "^$) - but...
removed other case, found where that data came from and it was on me.
- Dominant language
- JavaScript
- Stars
- 131
- Forks
- 46
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from mapbox/dynamodb-replicator
-
Difficulty 3/5 1-2 days Newbie friendliness 25/100
mapbox/dynamodb-replicator#109 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 48/100
mapbox/dynamodb-replicator#107 ·
-
Not usable toolOpen
Difficulty 5/5 Over a week Newbie friendliness 25/100
mapbox/dynamodb-replicator#105 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
mapbox/dynamodb-replicator#104 ·
-
Difficulty 5/5 Over a week Newbie friendliness 15/100
mapbox/dynamodb-replicator#101 · 1 comment ·
All issues in mapbox/dynamodb-replicator
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
hexlet-codebattle/codebattle#2361 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
micromatch/picomatch#223 ·
Maintainers usually reply within 11 days
-
Upgrade MongoDB Node.js driver to 7.6+ for full MongoDB 9.0 compatibilityPossibly taken @ga262 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
parse-community/parse-server#10754 · 1 comment ·
Maintainers usually reply within 1 day
-
🐛 bug
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
margelo/react-native-vision-camera#4211 ·
Maintainers usually reply within 4 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
platformatic/platformatic#5161 · 1 comment ·
Maintainers usually reply within 1 day