Skip to content

docs: update ResultSet.current_rows wrt empty pages #472

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

Merged
merged 1 commit into from
May 29, 2025

Conversation

avikivity
Copy link
Member

ScyllaDB may send empty pages when processing long spans of tombstones to avoid timing out; adjust the documentation not to imply that an empty page means there is no more data.

Pre-review checklist

  • I have split my patch into logically separate commits.
  • All commit messages clearly explain what they change and why.
  • I added relevant tests for new features and bug fixes.
  • All commits compile, pass static checks and pass test.
  • PR description sums up the changes and reasons why they should be introduced.
  • I have provided docstrings for the public items that I want to introduce.
  • I have adjusted the documentation in ./docs/source/.
  • I added appropriate Fixes: annotations to PR description.

ScyllaDB may send empty pages when processing long spans of
tombstones to avoid timing out; adjust the documentation not
to imply that an empty page means there is no more data.
@roydahan roydahan merged commit 30f6d78 into scylladb:master May 29, 2025
14 of 18 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants