-
Notifications
You must be signed in to change notification settings - Fork 2k
feat: add scoped physical expression traversal #21386
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
rluvaton
wants to merge
17
commits into
apache:main
Choose a base branch
from
rluvaton:add-support-for-scoped-traversal
base: main
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.
Open
Changes from all commits
Commits
Show all changes
17 commits
Select commit
Hold shift + click to select a range
79c78e6
add test that column in different scope should not be used for case when
rluvaton 18f5cd6
add tree scope
rluvaton 94fb0c3
make the test actually fail on main
rluvaton c8d2648
add tests
rluvaton b6383cc
remove outdated column
rluvaton d981a15
add tests
rluvaton 25fcc4a
lint and format
rluvaton 984076b
update comments
rluvaton 864cec3
update comment
rluvaton fdb1f9d
Update tree_node.rs
rluvaton 9221b1f
fix clippy and update comment
rluvaton e9200ac
rename
rluvaton e817a7e
update
rluvaton bfc9db9
update comment
rluvaton b0b8d85
renamed
rluvaton 7b9fc25
simplify tree node tests by asserting that scoped result are the same as
rluvaton 11d7e79
avoid clone
rluvaton 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
Large diffs are not rendered by default.
Oops, something went wrong.
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
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.
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.
Uh oh!
There was an error while loading. Please reload this page.
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 think this API is confusing because "scope" isn't something that is defined
I think a beter description of what this API is doing is "children in the outermost scope"
All built in expressions have the (implicit) property that their children are evaluated in the same input schema. I don't see how
CASEis any different in theory (though I understand it is what is causing you current problems)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 also think if we add thsi API it is easy to misue and you'll be chasing down corner case bugs with other expression types that have the same problem