You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
(this might be a duplicate of #89 but I'm not completely sure as this is also related to query methods)
Expected Behavior
Repository should consider Pageable object and AWS API calls should have the Limit param.
Actual Behavior
When using Pageable objects in repository methods, spring data seems to be ignoring the page request. When limiting the results via the query method name (such as findTopYByX) the results seems to be limited, but by looking at AWS SDK logs, the actual query sent to DynamoDB actually has no Limit param so I suppose the limit is done in memory.
Steps to Reproduce the Problem
Given a Java project with spring boot, lombok, junit 5 and proper logging configured, the following classes will demonstrate the problem:
Yes, you are correct.
Limit has been added via #239 and will be part of 5.1.1 Pageable has a PR I'm working (#117) so that will be supported in the near future, too.
No, I didn't. In the end we migrated our code to use the dynamo mapper lib
officially supported by aws.
Em dom, 12 de mai de 2019 20:12, Khangaldyan <[email protected]>
escreveu:
(this might be a duplicate of #89 but I'm not completely sure as this is also related to query methods)
Expected Behavior
Repository should consider
Pageable
object and AWS API calls should have theLimit
param.Actual Behavior
When using
Pageable
objects in repository methods, spring data seems to be ignoring the page request. When limiting the results via the query method name (such asfindTopYByX
) the results seems to be limited, but by looking at AWS SDK logs, the actual query sent to DynamoDB actually has noLimit
param so I suppose the limit is done in memory.Steps to Reproduce the Problem
Given a Java project with spring boot, lombok, junit 5 and proper logging configured, the following classes will demonstrate the problem:
The output can be checked here: https://gist.github.com/csokol/f6b88e7f55002f80150ebdf5f8ca7d6a
By looking at lines 94 and 118 of the gist. It's possible to see that the queries are sent without the
Limit
param.Specifications
The text was updated successfully, but these errors were encountered: