[
https://issues.apache.org/jira/browse/KYLIN-2679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16064087#comment-16064087
]
Shaofeng SHI commented on KYLIN-2679:
-------------------------------------
Thanks Kaisen; The change in KYLIN-2316 helps to some extends.
But the problem wasn't fixed. With Kylin 2.0, I define the dimension column to
use a normal dict, and in the bitmap measure, I define to use GD, then I will
get the error "ERROR : Global dictionary couldn't be used for dimension column:
DEFAULT.KYLIN_SALES.SELLER_ID". This is wrong as I wasn't trying to use GD only
for dimension encoding.
Even if I change the dimension column to use "fixed_length:4" encoding, it
still reports the same error, this causes mis-leading. I reproduced this with
the sample model. The check need be improved.
> Report error when a dimension using "dict" encoding and also configured
> Global dictionary for "distinct_count" measure
> ----------------------------------------------------------------------------------------------------------------------
>
> Key: KYLIN-2679
> URL: https://issues.apache.org/jira/browse/KYLIN-2679
> Project: Kylin
> Issue Type: Bug
> Components: Metadata, Query Engine
> Reporter: Shaofeng SHI
>
> This is a problem reported by community user Sonny Heer:
> After finally getting the global dictionary to work with building the cube
> there are now exceptions during query.
> ERROR in query: "AppendTrieDictionary can't retrive value from id"
> The cube has a UHC dimension, which also appeared in a count distinct
> measure. Then a global dictionary is created for it, but Global dictionary
> doesn't support decoding, then there is such an error during query time.
> While this wasn't even checked when the cube is created.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
