[
https://issues.apache.org/jira/browse/KYLIN-4076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenchen updated KYLIN-4076:
----------------------------
Attachment: image-2019-07-09-17-15-18-516.png
Description:
in this version,
In SQL statements with case-when, when the name of the field is the same as
that of the case-when-as field, the result of the query is not converted to the
corresponding string.
But when I put the case when outside the braces, the query was correct again.
I suspect that "group by" has changed the order in which SQL is executed.
I wonder if there is a lack of configuration when I upgrade?
was:
in this version,
In SQL statements with case-when, when the name of the field is the same as
that of the case-when-as field, the result of the query is not converted to the
corresponding string.
I wonder if there is a lack of configuration when I upgrade?
> calcite parse in case when
> ---------------------------
>
> Key: KYLIN-4076
> URL: https://issues.apache.org/jira/browse/KYLIN-4076
> Project: Kylin
> Issue Type: Bug
> Affects Versions: v2.6.3
> Reporter: chenchen
> Priority: Major
> Attachments: image-2019-07-09-16-16-16-162.png,
> image-2019-07-09-16-19-09-420.png, image-2019-07-09-17-15-18-516.png
>
>
> in this version,
> In SQL statements with case-when, when the name of the field is the same as
> that of the case-when-as field, the result of the query is not converted to
> the corresponding string.
> But when I put the case when outside the braces, the query was correct again.
> I suspect that "group by" has changed the order in which SQL is executed.
> I wonder if there is a lack of configuration when I upgrade?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
