-
Notifications
You must be signed in to change notification settings - Fork 59
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
Paginator returning less data than actually have #159
Comments
ScyllaDB may return a smaller page than requested in order to avoid high memory usage. This can happen if
This is normal and shouldn't present a performance problem. It does add latency, but scans should be performed in parallel so the server has other queries to process while the data is in transit. |
Thanks for the reply @avikivity.
nodetool tablestats
Adding more context for the table and view:
I also tried to run with tracing, I'm supposed to have 207 rows in the following query, running with LIMIT 205 is fine, but running with LIMIT 206 will take a huge long time: Running query with tracing
|
But the go code still won’t bring these two rows, if I put limit |
@caevv , can you please show the code on how do you iterate over iter.PageState() ? |
Please answer these questions before submitting your issue. Thanks!
What version of Scylla or Cassandra are you using?
Scylla 5.2.15
What version of Gocql are you using?
1.12.0
What version of Go are you using?
1.21
I am experiencing an issue with pagination. Despite there being more data to fetch using PageSize() will return a value smaller than what is set, iter.PageState() will have some data, but calling with the returned token on PageState will return empty data, but I know there are more rows in the table.
Additional Observations:
Attempted Solutions:
Questions/Help Needed:
Any insights or suggestions from the community would be greatly appreciated. Thank you!
The text was updated successfully, but these errors were encountered: