Re: Re: java.lang.RuntimeException:unexpectedevictreasonCOLLECTED

2018-09-25 Thread huanli
I'm the same with you. I ensure that I didn't use the Dim columns for global dictionary. but this error happened incidentally. I change the name of fact table, and then it build sucess! -- Sent from: http://apache-kylin.74782.x6.nabble.com/

Re: Re: java.lang.RuntimeException:unexpectedevictreasonCOLLECTED

2018-03-02 Thread Li Yang
Pls post some logs or others cannot help. On Tue, Feb 27, 2018 at 5:07 PM, jun <1063489...@qq.com> wrote: > It is a bug or some reason ? > > -- > Sent from: http://apache-kylin.74782.x6.nabble.com/ >

Re: Re: java.lang.RuntimeException:unexpectedevictreasonCOLLECTED

2018-02-27 Thread jun
It is a bug or some reason ? -- Sent from: http://apache-kylin.74782.x6.nabble.com/

Re: Re: java.lang.RuntimeException:unexpectedevictreasonCOLLECTED

2018-02-27 Thread jun
I have encounter this problem. -- Sent from: http://apache-kylin.74782.x6.nabble.com/

Re: Re: java.lang.RuntimeException:unexpectedevictreasonCOLLECTED

2017-02-12 Thread 446463...@qq.com
I kown this.in my scene ,I ensure that I didn't use the Dim columns for global dictionary. but this error happened incidentally 446463...@qq.com From: Alberto Ramón Date: 2017-02-12 18:20 To: dev Subject: Re: Re: java.lang.RuntimeException:unexpectedevictreasonCOLLECTED

Re: Re: java.lang.RuntimeException:unexpectedevictreasonCOLLECTED

2017-02-12 Thread Alberto Ramón
https://issues.apache.org/jira/browse/KYLIN-2316?focusedCommentId=15857574&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15857574 This error only happens if you used global dicctionary on Dim Colum 2017-02-12 10:57 GMT+01:00 446463...@qq.com <446463...@qq.com>: >

Re: Re: java.lang.RuntimeException:unexpectedevictreasonCOLLECTED

2017-02-12 Thread 446463...@qq.com
thx.But I rebuild the cube,it is scueessful.What happened? 446463...@qq.com From: Alberto Ramón Date: 2017-02-12 17:34 To: dev Subject: Re: java.lang.RuntimeException:unexpectedevictreasonCOLLECTED Exactly, this patch has been apply only to 2.0.0 (*"Fix Version/s:* v2.0.0"