[
https://issues.apache.org/jira/browse/KYLIN-2177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15661149#comment-15661149
]
Shaofeng SHI commented on KYLIN-2177:
-------------------------------------
Hi chao, could you please paste the full error trace? In my mind it is the same
issue as KYLIN-1967, which was a bug when there is an empty segment. Kylin
1.6.0 has the patch so you can download the 1.6.0-SNAPSHOT package to have a
quick verification.
> dict.TrieDictionary:182 : Not a valid value: 2016-11-13
> -------------------------------------------------------
>
> Key: KYLIN-2177
> URL: https://issues.apache.org/jira/browse/KYLIN-2177
> Project: Kylin
> Issue Type: Improvement
> Components: Metadata
> Reporter: huangchao
> Assignee: Shaofeng SHI
> Attachments: Snip20161113_11.png, Snip20161113_12.png
>
>
> version :apache-kylin-1.5.4.1-hbase1.x-bin
> os:ubuntu 14.04.1
> insight return below error after retrigger cube job.
> "Error while executing SQL "select * from sale_detail LIMIT 50000":
> java.lang.IllegalArgumentException: Value not exists!"
> step:
> drop exist cube then recreate job, insight work well when exist "select *
> from sale_detail LIMIT 50000".
> then exist cube build for new data. insight broken and thrown below issue
> "select * from sale_detail LIMIT 50000": java.lang.IllegalArgumentException:
> Value not exists!"
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
