-
Notifications
You must be signed in to change notification settings - Fork 2.3k
refactor(unparser): centralize aggregate-scope rendering in the SQL unparser #23789
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
naman-modi
wants to merge
6
commits into
apache:main
Choose a base branch
from
naman-modi:refactor/unparser-agg-scope
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.
+231
−55
Open
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
5483a1d
refactor(unparser): centralize aggregate-scope rendering in the SQL u…
naman-modi 542891d
Merge branch 'main' into refactor/unparser-agg-scope
naman-modi ef910d7
nit(refactor unparser): address review comments
naman-modi 5f5c5c6
Merge branch 'main' into refactor/unparser-agg-scope
naman-modi b6cd840
Merge branch 'main' into refactor/unparser-agg-scope
naman-modi 7009568
Merge branch 'main' into refactor/unparser-agg-scope
naman-modi 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
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 like
UnparserAggScopeas a small abstraction because it naturally ties an aggregate to its derived-input scope decision.One small thing that stood out is
prepare_sort_expr(scope: Option<&Self>, ...). TheNonecase doesn't really have an aggregate scope, so it feels like the abstraction is carrying a responsibility outside its model.Would it make sense to keep aggregate normalization as an instance method and move the optional sort orchestration into an
Unparserhelper, or simply split the aggregate and non-aggregate paths? I think that would keep the responsibilities a bit more focused. Just a small design suggestion.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.
Makes sense, I have updated the
prepare_sort_exprto now be an instance method ofUnparserAggScope, and created aUnparser::unproject_sort_expr_in_scopeto handle both the arms, hence unifying the call sites.