[
https://issues.apache.org/jira/browse/BEAM-9075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17142287#comment-17142287
]
Beam JIRA Bot commented on BEAM-9075:
-------------------------------------
This issue is P2 but has been unassigned without any comment for 60 days so it
has been labeled "stale-P2". If this issue is still affecting you, we care!
Please comment and remove the label. Otherwise, in 14 days the issue will be
moved to P3.
Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed
explanation of what these priorities mean.
> Join re-ordering doesn't work for ZetaSQL
> -----------------------------------------
>
> Key: BEAM-9075
> URL: https://issues.apache.org/jira/browse/BEAM-9075
> Project: Beam
> Issue Type: Bug
> Components: dsl-sql-zetasql
> Affects Versions: 2.17.0
> Reporter: Brian Hulette
> Priority: P2
> Labels: stale-P2
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> Join re-ordering can actually break queries in the ZetaSQL planner because
> Calcite's JoinCommuteRule doesn't work when schemas have nested fields. It
> only adjusts RexInputRef nodes and not RexFieldAccess.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)