You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@kylin.apache.org by "liyang (Jira)" <ji...@apache.org> on 2022/10/02 01:58:00 UTC

[jira] [Commented] (KYLIN-5272) The "case when" command may cause the field value to be different from the user's expectation.

    [ https://issues.apache.org/jira/browse/KYLIN-5272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17612006#comment-17612006 ] 

liyang commented on KYLIN-5272:
-------------------------------

Could you provide a complete SQL and related table structure, such that others can reproduce the issue and then be able to help?

Also likely, without knowing the exact problem, the issue maybe fixed in Kylin 4.x as all calculations are moved into Spark. Calcite is only used for SQL parsing.

> The "case when" command may cause the field value to be different from the user's expectation.
> ----------------------------------------------------------------------------------------------
>
>                 Key: KYLIN-5272
>                 URL: https://issues.apache.org/jira/browse/KYLIN-5272
>             Project: Kylin
>          Issue Type: Bug
>          Components: Query Engine
>    Affects Versions: v2.2.0, v2.6.3
>            Reporter: GuKe
>            Priority: Major
>         Attachments: issue.jpg
>
>
> When using "Case then" to set a fixed character value for a field, Kylin uses Spaces to complete the length of string to 32. This will cause the field to display characters that are actually different from the user's expected values, causing query errors, Example a failed Join operation.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)