-
-
Notifications
You must be signed in to change notification settings - Fork 365
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
Automatic pagination/aggregation for Query and Scan #102
Comments
If you wonder which |
I overlooked this. That would be great. Let me know if you need any help. |
Will work on it this weekend |
@brandongoode when this is going to come as a new version? |
@yusufar No ETA on the release date. I have to find some time to clean up some loose ends and then will be working on the next release. For now, you can pull directly from the repo. I try to make sure master is always stable, but I would recommend referencing a commit to make sure changes don't impact you. "dependencies": {
"package": "git://github.com/automategreen/dynamoose.git#commit"
} |
I'm going to implement automatic paginated request wrapper built-in in Query and Scan, because of DynamoDB chuck's size limit of 1Mb. Even if you just need to get a
count
of matching rows (without returning any other data), Query and Scan cannot return correct results in a single request if it goes thru more 1MB of data (keys or rows) on its side for analyzing. For examplecount
will be unaggregated. Pretty hard to demonstrate it using tests, because I need to feed a test DB with 10's of thousands rows in order for an index footprint to overflow 1Mb.The text was updated successfully, but these errors were encountered: