You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kylin.apache.org by "Yaqian Zhang (Jira)" <ji...@apache.org> on 2019/09/25 06:31:00 UTC
[jira] [Commented] (KYLIN-4076) calcite parse in case when
[ https://issues.apache.org/jira/browse/KYLIN-4076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16937442#comment-16937442 ]
Yaqian Zhang commented on KYLIN-4076:
-------------------------------------
Hi chenchen:
Thank you for your report.
I reproduced the problem you described and I think the parse of CASE WHEN in kylin have some bug.
We will fix these bugs in future version.
> 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
(v8.3.4#803005)