[logical] Introducing physical optimizer support for logical tables #17447
+657
−7
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.
Summary
This PR enables the physical optimizer to work correctly with logical tables by making the physical planning and worker assignment logic aware of logical to physical table mappings.
The leaf-stage worker assignment is updated to resolve logical tables, compute routing across all underlying physical tables, and produce deterministic worker to segment assignments, while fragment metadata is extended to carry logical-table specific segment mappings.
Figuring out a way to assign distribution for a logical table still needs some investigation - hence will be picked up in a follow-up PR.
Testing
Adds integration coverage to validate that common query patterns work with logical tables under the physical optimizer. Also added unit tests.