[
https://issues.apache.org/jira/browse/CALCITE-4620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17351260#comment-17351260
]
Steven Talbot commented on CALCITE-4620:
----------------------------------------
I think that all makes sense. I certainly like taking out that giant switch
causing these problems. One thought [~julianhyde] should we not implement
SqlOperator.reverse() in terms of SqlKind.reverse(). Otherwise there are two
different sources of truth about what is "reversible". Though I wouldn't
exactly expect that list of reversible ops to change much, and maybe there's a
good reason for having it in both places.
> Join on CASE causes AssertionError in RelToSqlConverter
> -------------------------------------------------------
>
> Key: CALCITE-4620
> URL: https://issues.apache.org/jira/browse/CALCITE-4620
> Project: Calcite
> Issue Type: Bug
> Reporter: Steven Talbot
> Assignee: Julian Hyde
> Priority: Major
>
> Basically CALCITE-4610 but this time with a CASE WHEN.
> I can provide a repro test if needed, but any join with a condition like in
> that same test
> {code:java}
> CASE WHEN a = 'some_literal' THEN true ELSE c = 'some_other_literal' END{code}
> The CASE travels through the pipeline, and the RelToSqlConverter crashes on
> it in convertConditionToSqlNode.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
