Add integration test for IO operations for listing tables queries #18229
+617
−0
Conversation
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
github-actions
bot
added
core
alamb
force-pushed
the
alamb/object_store_trace_tests
branch
3 times, most recently
from
b2924b7 to
3db4b0e
Compare
alamb
force-pushed
the
alamb/object_store_trace_tests
branch
from
3db4b0e to
ba4e802
Compare
alamb
changed the title
alamb
force-pushed
the
alamb/object_store_trace_tests
branch
from
ba4e802 to
981bc5c
Compare
alamb
commented
Oct 24, 2025
| @r" | ||
| RequestCountingObjectStore() | ||
| Total Requests: 2 | ||
| - HEAD path=csv_table.csv |
There was a problem hiding this comment.
the idea is here we can see what object store requests are made for various operations
alamb
force-pushed
the
alamb/object_store_trace_tests
branch
from
981bc5c to
4b4a9ec
Compare
This was referenced Oct 24, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Which issue does this PR close?
Rationale for this change
As we spend more effort optimizing the number of IO requests made during various scenarios, we need to ensure we have test coverage to:
What changes are included in this PR?
Add a new integration test that verifies what IO operations happen when creating and querying listing tables
Are these changes tested?
It is all tests
Are there any user-facing changes?
No, only tests