[
https://issues.apache.org/jira/browse/BEAM-9075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17015357#comment-17015357
]
Rui Wang commented on BEAM-9075:
--------------------------------
Regarding to your option 2), we can reuse Calcite's struct flattener. However,
when we really want to start to support Struct, and deep nested Struct, I will
expect we need submit patches about struct flattener to Calcite to handle how
different corner cases (or we build in-house solution to avoid slower code
review process in Calcite repo). Option 2) is not a clean solution with less
trouble as I am seeing it now.
> 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
> Assignee: Brian Hulette
> Priority: Major
> 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)
