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
{{ message }}
Repository navigation
Commit efe6abd
Browse filesBrowse the repository at this point in the historyBrowse files
refactor: move lambda variable scope into Physical Planning Context (apache#23989)
## 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
`Closesapache#123` indicates that this PR will close issue apache#123.
-->
- Closesapache#23700 .
## Rationale for this change
<!--
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.
-->
This is a clean up following apache#23649
## What changes are included in this PR?
- Moves the lambda-variable scope state out of `ExecutionProps` and into
`PhysicalPlanningContext`, following the same pattern as the
scalar-subquery state in apache#23649.
- Puts `PhysicalPlanningContext::indexes` behind an `Arc` so the new
per-lambda-body clone doesn't deep-copy the subquery index map.
`PhysicalPlanningContext::new`'s signature is unchanged.
## Are these changes tested?
- New `lambda_variables_shadow_outer_scope` unit test in
`physical_planning_context.rs` covers `with_qualified_lambda_variables`
/ `lambda_variable_qualifier` directly, including an inner lambda
shadowing an outer parameter name.
## Are there any user-facing changes?
this is a breaking change for lib users.
0 commit comments