forked from apache/cassandra-python-driver
-
Notifications
You must be signed in to change notification settings - Fork 49
Add paging with multi-page support to ControlConnection topology queries #637
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
Open
Copilot
wants to merge
9
commits into
master
Choose a base branch
from
copilot/update-internal-queries-paging
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+134
−11
Open
Changes from all commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
2e62804
Initial plan
Copilot a79e51d
Add fetch_size to ControlConnection topology queries
Copilot faa59e6
Improve test robustness based on code review feedback
Copilot 2dce180
Add proper paging support for ControlConnection topology queries
Copilot 10a6eaf
Address code review feedback
Copilot ef9dc96
Final code review fixes
Copilot 58bc51d
Clarify comment for consistency in paging call
Copilot d7ac847
Clarify comment about restoring paging_state
Copilot 4a715a3
Add clarifying comments about paging behavior
Copilot File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't see any support for paging in
connection.wait_for_responses, which is used here. Won't this just query just a first page and ignore subsequent pages? cc @dkropachevThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@copilot - please respond to the above feedback.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You're absolutely right! I've addressed this by implementing a
_fetch_all_pageshelper method that properly handles paging by fetching all pages, not just the first one. The implementation now:wait_for_responsespaging_statein the resultwait_for_responsewith the paging_stateThis ensures all nodes are discovered in large clusters (>1000 nodes) while still using paging to avoid unpaged query metrics.
Changes in commit ef9dc96.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@copilot and is there any test for the new functionality?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, there are two comprehensive unit tests added in commit 2dce180:
test_topology_queries_use_paging- Verifies that all topology queries have thefetch_sizeparameter set correctlytest_topology_queries_fetch_all_pages- Verifies that the_fetch_all_pagesmethod properly handles multi-page results by:Both tests pass successfully (24 total tests in test_control_connection.py).