The RestoreTableFromBackup response for a PROVISIONED table has no BillingModeSummary and no NumberOfDecreasesToday, where DynamoDB sends both
Maintainers usually reply within 5 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 78/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- mongodb, postgresql, rust, sqlite
- Domain
- backend-api-design, database
Research direction
Read crates/engine/src/backup.rs, focusing on restore_response and its doc comment. Check how the function builds the response from the backend description for a PROVISIONED target; the issue proposes setting BillingModeSummary and NumberOfDecreasesToday to 0. Done when the restore response includes both members and the comment matches observed behavior; the issue does not name a test to run.
Written by the indexing model from the issue text.
Description
DynamoDB's RestoreTableFromBackup response for a backup of a PROVISIONED table carries "BillingModeSummary": {"BillingMode": "PROVISIONED"}, and "NumberOfDecreasesToday": 0 in ProvisionedThroughput. ExtendDB's response has neither member, on SQLite, PostgreSQL, MongoDB and Cassandra. Apart from these two, the TableDescription of the response has the same members on both sides.
Measured in us-east-1 on 20 Nov 2026, twice, with the same answers both times. Each run created a PROVISIONED 5/7 table keyed on pk (S), raised it to 9/11, waited for ACTIVE, made a backup and restored it to a new table.
TableDescription member of the RestoreTableFromBackup response |
DynamoDB | ExtendDB |
|---|---|---|
BillingModeSummary |
{"BillingMode": "PROVISIONED"} |
absent |
ProvisionedThroughput |
{"NumberOfDecreasesToday": 0, "ReadCapacityUnits": 9, "WriteCapacityUnits": 11} |
{"ReadCapacityUnits": 9, "WriteCapacityUnits": 11} |
The DescribeTable of the restored table once ACTIVE carries no BillingModeSummary on DynamoDB either, so only the response differs there. Its NumberOfDecreasesToday is a separate difference, in #1197.
ExtendDB ran on the fix for #1035, stacked on #1093's head 8ec2603ea, on all four backends, and on #1093's head on SQLite. All of them gave the answer above.
restore_response in crates/engine/src/backup.rs builds the response from the backend's description. Its doc comment says that DynamoDB omits ProvisionedThroughput.NumberOfDecreasesToday from this response. On 20 Nov DynamoDB sent it in both runs. The backends describe a PROVISIONED table with no BillingModeSummary, and the function keeps what the backend gives.
Proposed change: in restore_response, set BillingModeSummary with BillingMode PROVISIONED and send NumberOfDecreasesToday 0 for a PROVISIONED target, and correct the doc comment. A restore to a PAY_PER_REQUEST target was not measured in this run.
- Dominant language
- Rust
- Stars
- 517
- Forks
- 60
- Avg merge
- 4d 23h
- Merged PRs (30d)
- 134
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a 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 ExtendDB/extenddb
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 5 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 5 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 5 days
-
Cassandra: destroy lists no catalog table before --yes, because Cassandra refuses the listing queryOpen
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 5 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
Maintainers usually reply within 5 days
All issues in ExtendDB/extenddb
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
bytecodealliance/wrpc#1785 ·
Maintainers usually reply within 1 day
-
2 advisory ignore entries no longer match anything (`quick-xml` already patched in `Cargo.lock`)Open
Difficulty 1/5 Under an hour Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
longbridge/nsh#2758 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
antithesishq/bombadil#473 ·
Maintainers usually reply within 2 days
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
libracoder/kiri#669 ·
Maintainers usually reply within 1 day