-
Notifications
You must be signed in to change notification settings - Fork 63
refactor: ExecuteResult is reusable, sampleable #2159
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
Changes from all commits
Commits
Show all changes
26 commits
Select commit
Hold shift + click to select a range
ca51638
refactor: ExecuteResult is reusable, sampleable
TrevorBergeron 6d16001
refactor data source classes
TrevorBergeron 5afbb2d
refactor result size statistics
TrevorBergeron 703fd7e
refactor materialization type normalize steps
TrevorBergeron a93808a
fix read session config
TrevorBergeron bea592c
push data normalization into managed table init
TrevorBergeron b9b8692
fix broken tests
TrevorBergeron 6e53541
fix read api invocation
TrevorBergeron 71fa69d
add validation to bq source
TrevorBergeron cf3b7e3
add debug validation
TrevorBergeron bdb1476
fix result schema extra column handling
TrevorBergeron bf8c827
fix results bytes estimate
TrevorBergeron 1f85658
fix name mappings for remote sources
TrevorBergeron 628363b
refactor query metadata
TrevorBergeron b890d4b
fix execution metadata
TrevorBergeron 9c04587
Merge remote-tracking branch 'github/main' into new_execute_result
TrevorBergeron eb5cb76
avoid read api where result small
TrevorBergeron b5e35fa
Merge remote-tracking branch 'github/main' into new_execute_result
TrevorBergeron 91157fb
fix mock execute result in test
TrevorBergeron 5e5892f
Merge remote-tracking branch 'github/main' into new_execute_result
TrevorBergeron c316830
fix cluster col limit appliction
TrevorBergeron 46334da
fix schema loacing
TrevorBergeron 1cdf793
Merge remote-tracking branch 'github/main' into new_execute_result
TrevorBergeron 4acf103
fix unit test
TrevorBergeron 235e5e5
read parallel consumer fixes
TrevorBergeron 52bce76
fix extension type issue
TrevorBergeron 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.
As we discussed offline, I think it'd be helpful to have cases where we know (or at least have very high confidence) of this being exact, such as when reading the destination table of a query.
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.
We do insert row count directly in the tree when known exactly (or at least some of the time we know exactly, might be missing some opportunities). At a certain point we just intermingle known and approx though, before surfacing. Could keep separate if really needed, but a bit more complexity.