You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix(aggregate): show aliased expr in explain (#21739)
## Which issue does this PR close?
<!--
We generally require a GitHub issue to be filed for all bug fixes and
enhancements and this helps us generate change logs for our releases.
You can link an issue to this PR using the GitHub syntax. For example
`Closes#123` indicates that this PR will close issue #123.
-->
- Closes#19685.
## Rationale for this change
Physical explain output only showed the alias for aliased aggregates.
That made it hard to understand the plan, especially when the aggregate
had a filter, explicit RESPECT NULLS, or a custom UDAF display.
<!--
Why are you proposing this change? If this is already explained clearly
in the issue then this section is not needed.
Explaining clearly why changes are proposed helps reviewers understand
your changes and offer better suggestions for fixes.
-->
## What changes are included in this PR?
- Show the full aggregate expression in physical explain for
user-written aggregate aliases.
- Keep internal aliases like count(*) compact in physical explain.
- Replace the old hidden metadata approach with an explicit is_internal
flag on Alias.
- Preserve that flag through planner rewrites, tree rewrites, and proto
round-trip.
- Add tests for aliased aggregate explain output, including:
- normal aliased aggregates
- quoted aliases
- explicit RESPECT NULLS
- custom human display
- count(*)
- nested internal alias display
- Add an upgrade note for the public Alias API change.
<!--
There is no need to duplicate the description in the issue here but it
is sometimes worth providing a summary of the individual changes in this
PR.
-->
## Are these changes tested?
Yes
<!--
We typically require tests for all PRs in order to:
1. Prevent the code from being accidentally broken by subsequent changes
2. Serve as another way to document the expected behavior of the code
If tests are not included in your PR, please explain why (for example,
are they covered by existing tests)?
-->
## Are there any user-facing changes?
Yes.
- Physical explain output is clearer for aliased aggregate expressions.
- Alias now has a new is_internal field.
This is a public API change for users who build or pattern match Alias
directly. The upgrade guide has been updated with the needed changes.
<!--
If there are user-facing changes then we may require documentation to be
updated before approving the PR.
-->
<!--
If there are any breaking changes to public APIs, please add the `api
change` label.
-->
0 commit comments