[CALCITE-7085] JOIN USING with unqualified common column fails in a conformance where allowQualifyingCommonColumn is false (e.g. Oracle, Presto)#4912
Conversation
…onformance where allowQualifyingCommonColumn is false (e.g. Oracle, Presto)
cjj2010
changed the title
| new SqlIdentifier( | ||
| ImmutableList.of(child.name, name), | ||
| identifier.getParserPosition()); | ||
| SqlParserPos.ZERO); |
There was a problem hiding this comment.
This does not look like a robust way to carry information between compilation stages; in general, the parser position is best-effort in Calcite.
There must be a better way to do this. My intuition tells me that the unparser has to handle this case by stripping out the qualifying information. Alternatively, can the join type be changed to an INNER JOIN?
There was a problem hiding this comment.
Thank you for your suggestion. The original plan was indeed inadequate. I have now revised it to completely separate validation from expansion — validating the original AST once before expansion, and not performing validation during expansion.
…n column handling
|
2 participants
jira: https://issues.apache.org/jira/browse/CALCITE-7085