Consumed Capacity for batchGetAll is incorrect
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 79
- Forks
- 27
- PR merge metrics
- No merged PRs in 30d
Description
**Params**
``` json
{
"ReturnConsumedCapacity":"TOTAL",
"RequestItems":{
"cardboard-search":{
"Keys":[
{
"id":"test!bbox!state",
"search":"feature"
}
]
}
}
}
```
**Result**
``` json
{
"Responses":{
"cardboard-search":[
{
"id":"test!bbox!state",
"search":"feature",
"quadkeys":[
"03313302"
]
}
]
},
"UnprocessedKeys":{ },
"ConsumedCapacity":{ }
}
```
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 the batchGetAll implementation and trace how ReturnConsumedCapacity is handled for the request and response shown in this issue. Compare the returned ConsumedCapacity with the expected DynamoDB behavior and add or update a relevant test; done means batchGetAll reports capacity when TOTAL is requested.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100