DynamoDB Table Resource should support Pagination for Scan and Query

The boto3 “Table” Resource API does not provide easy access to paged results when using Scan or Query actions. That’s unlike other high level boto3 Resource APIs like S3 which supports s3.Bucket('bucket').objects.pages().

The underlying DynamoDB client supports pagination, which leaves the boto3 user with the choice between nice attribute access + ugly pagination or ugly attribute access + nice pagination, which is unfortunate.

[aBurmeseDev]

Thank you all for checking in and apologies for the delay.

We created a backlog item to look into this feature request and if anyone wants to share additional use cases or feedback then please feel free to leave a comment. Although we can’t give a definite timeline at the moment, we’ll make sure to keep it posted as soon as we have an update and please feel free to check back here in the future.

[tomislacker]

@rbu Thank you much for this, I’m also interested. I’m surprised by there being relatively little activity on this issue. But I suppose if the consumers of DynamoDB that aren’t using some sort of ORM already are the main ones affected; I’m not really surprised. They’re already dealing a lot with some gnarly JSON blobs.