-
Couldn't load subscription status.
- Fork 139
@Query annotation to support query limiting #226
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
Conversation
A little look at how my query results return look based on this now. Also usage metrics are way down.
Codecov Report
@@ Coverage Diff @@ ## master #226 +/- ## ============================================ + Coverage 67.31% 67.36% +0.05% - Complexity 656 658 +2 ============================================ Files 83 83 Lines 2227 2246 +19 Branches 392 393 +1 ============================================ + Hits 1499 1513 +14 - Misses 549 553 +4 - Partials 179 180 +1
Continue to review full report at Codecov.
|
A look at GSI read metrics after deployment.
merging back
Thank you so much.
Merged via #239
This will allow you to limit the results returned from a DynamoDB query that has a sort and range key, techincally also a Scan. I developed this to reduce cost b ased on the new OnDemand pricing.
Example:
The previous behavior would actually return every single result and then clip it. With this limit parameter dynamo only returns the request amount of results. This is mainly for HashAndRange. It still requires First10 and the Query annotation to work otherwise the Spring-DynamoDB will just do queries limited to 10 results until it gets them all.