-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DynamoDB.Table.batch_reader()? #1068
Comments
I think this would be useful. Marking as feature request. |
This is really needed, because the high level abstraction that Table has saves so much time (auto typing). Extra points for automatically handling pagination |
This has been open since 2017. Is it getting prioritized? Has anyone written a little library they've released to make up for the lack of a batch_reader? |
The boto3 team has recently announced that the Resource interface has entered a feature freeze and won’t be accepting new changes at this time: https://boto3.amazonaws.com/v1/documentation/api/latest/guide/resources.html. We’ll be closing existing feature requests, such as this issue, to avoid any confusion on current implementation status. We do appreciate your feedback and will ensure it’s considered in future feature decisions. We’d like to highlight that all existing code using resources is supported and will continue to work in Boto3. No action is needed from users of the library. |
A reader / getter version of
DynamoDB.Table.batch_writer()
would be useful. It would be a new methodDynamoDB.Table.batch_reader()
.The current alternative is to use either multiple calls of
DynamoDB.Table.get_item()
or a single call ofDynamoDB.Client.batch_write_item()
.The downsides of using the client-type are
it returns DynamoDB JSON instead of standard JSON (but this can be worked around using
resource.meta.client.batch_get_item
as per this PR)it does not automatically handle buffering with respect to read capacities as the
DynamoDB.Table.batch_writer()
does.The text was updated successfully, but these errors were encountered: