[jira] [Commented] (KYLIN-2251) JDBC Driver httpcore dependency conflict
[ https://issues.apache.org/jira/browse/KYLIN-2251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15739320#comment-15739320 ] hongbin ma commented on KYLIN-2251: --- thx for the explanation > JDBC Driver httpcore dependency conflict > > > Key: KYLIN-2251 > URL: https://issues.apache.org/jira/browse/KYLIN-2251 > Project: Kylin > Issue Type: Bug > Components: Driver - JDBC >Affects Versions: v1.6.0 >Reporter: Billy Liu >Assignee: Billy Liu >Priority: Minor > Fix For: v1.6.1 > > > Report by xwhfcenter from github: > "There is a conflict in dependency of httpcore in module JDBC Driver" -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (KYLIN-2144) move useful operation tools to org.apache.kylin.tool
[ https://issues.apache.org/jira/browse/KYLIN-2144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15739327#comment-15739327 ] hongbin ma edited comment on KYLIN-2144 at 12/11/16 8:11 AM: - Actually the refactor did NOT remove the legacy implementation. If you find for example MetadataCleanupJob in the code repo, you will find two. one deprecated and one active. The deprecated class is left there intentionally for legacy users was (Author: mahongbin): Actually the refactor did NOT remote the legacy implementation. If you find for example MetadataCleanupJob in the code repo, you will find two. one deprecated and one active. The deprecated class is left there intentionally for legacy users > move useful operation tools to org.apache.kylin.tool > > > Key: KYLIN-2144 > URL: https://issues.apache.org/jira/browse/KYLIN-2144 > Project: Kylin > Issue Type: Improvement >Reporter: hongbin ma >Assignee: hongbin ma > Fix For: v1.6.1 > > > due to historical reasons, the following 5 operation tools: > StorageCleanupJob,MetadataCleanupJob,CubeMigrationCLI, > CubeMigrationCheckCLI,ExtendCubeToHybridCLI > locates in org.apache.kylin.storage.hbase.util, which brings dependency > issues and other concerns. > In 1.6.1 and later, we'll move the 5 tools to org.apache.kylin.tool. The old > java class will mark as deprecated, and no longer under maintainance. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KYLIN-2144) move useful operation tools to org.apache.kylin.tool
[ https://issues.apache.org/jira/browse/KYLIN-2144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15739327#comment-15739327 ] hongbin ma commented on KYLIN-2144: --- Actually the refactor did NOT remote the legacy implementation. If you find for example MetadataCleanupJob in the code repo, you will find two. one deprecated and one active. The deprecated class is left there intentionally for legacy users > move useful operation tools to org.apache.kylin.tool > > > Key: KYLIN-2144 > URL: https://issues.apache.org/jira/browse/KYLIN-2144 > Project: Kylin > Issue Type: Improvement >Reporter: hongbin ma >Assignee: hongbin ma > Fix For: v1.6.1 > > > due to historical reasons, the following 5 operation tools: > StorageCleanupJob,MetadataCleanupJob,CubeMigrationCLI, > CubeMigrationCheckCLI,ExtendCubeToHybridCLI > locates in org.apache.kylin.storage.hbase.util, which brings dependency > issues and other concerns. > In 1.6.1 and later, we'll move the 5 tools to org.apache.kylin.tool. The old > java class will mark as deprecated, and no longer under maintainance. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (KYLIN-2144) move useful operation tools to org.apache.kylin.tool
[ https://issues.apache.org/jira/browse/KYLIN-2144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] hongbin ma resolved KYLIN-2144. --- Resolution: Fixed > move useful operation tools to org.apache.kylin.tool > > > Key: KYLIN-2144 > URL: https://issues.apache.org/jira/browse/KYLIN-2144 > Project: Kylin > Issue Type: Improvement >Reporter: hongbin ma >Assignee: hongbin ma > Fix For: v1.6.1 > > > due to historical reasons, the following 5 operation tools: > StorageCleanupJob,MetadataCleanupJob,CubeMigrationCLI, > CubeMigrationCheckCLI,ExtendCubeToHybridCLI > locates in org.apache.kylin.storage.hbase.util, which brings dependency > issues and other concerns. > In 1.6.1 and later, we'll move the 5 tools to org.apache.kylin.tool. The old > java class will mark as deprecated, and no longer under maintainance. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (KYLIN-2240) Add a toggle to ignore all cube signature inconsistency temporally
[ https://issues.apache.org/jira/browse/KYLIN-2240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] hongbin ma resolved KYLIN-2240. --- Resolution: Fixed Fix Version/s: v1.6.1 > Add a toggle to ignore all cube signature inconsistency temporally > -- > > Key: KYLIN-2240 > URL: https://issues.apache.org/jira/browse/KYLIN-2240 > Project: Kylin > Issue Type: New Feature >Reporter: hongbin ma >Assignee: hongbin ma > Fix For: v1.6.1 > > > cube signature helps to prevent ready cubes from being changed to broken > state. However it could be annoying in some rare cases, for example POC sites. > The toggle should NEVER be used for serious PROD deployment! -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (KYLIN-2236) JDBC statement.setMaxRows(10) is not working
[ https://issues.apache.org/jira/browse/KYLIN-2236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] hongbin ma resolved KYLIN-2236. --- Resolution: Fixed > JDBC statement.setMaxRows(10) is not working > > > Key: KYLIN-2236 > URL: https://issues.apache.org/jira/browse/KYLIN-2236 > Project: Kylin > Issue Type: Bug >Affects Versions: v1.6.0 >Reporter: hongbin ma >Assignee: hongbin ma > Fix For: v1.6.1 > > > some BI tools will use statement.setMaxRows(10) to function as limit clause. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (KYLIN-2031) some more DimensionEncoding
[ https://issues.apache.org/jira/browse/KYLIN-2031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] hongbin ma resolved KYLIN-2031. --- Resolution: Fixed Fix Version/s: v1.6.1 > some more DimensionEncoding > --- > > Key: KYLIN-2031 > URL: https://issues.apache.org/jira/browse/KYLIN-2031 > Project: Kylin > Issue Type: New Feature >Reporter: hongbin ma >Assignee: hongbin ma > Fix For: v1.6.1 > > > 1. for some use cases string value represent hash code is used. The string > only consist of [0~9A~F] (hex values), so two characters can be squashed into > one byte > 2. The current IntegerDimEnc does not support negative values, need another > IntegerDimEnc that supports negative values -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (KYLIN-2029) lookup table support count(distinct column)
[ https://issues.apache.org/jira/browse/KYLIN-2029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] hongbin ma resolved KYLIN-2029. --- Resolution: Fixed Fix Version/s: v1.6.1 > lookup table support count(distinct column) > --- > > Key: KYLIN-2029 > URL: https://issues.apache.org/jira/browse/KYLIN-2029 > Project: Kylin > Issue Type: Improvement > Components: Query Engine >Affects Versions: v1.5.4 >Reporter: Zhong,Jason >Assignee: hongbin ma > Fix For: v1.6.1 > > > Now for dimension column on fact table, we can write sql like 'select > count(distinct columnName)...', but on lookup table, it's not supported. > need to add this. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (KYLIN-2021) Cognos Issues
[ https://issues.apache.org/jira/browse/KYLIN-2021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] hongbin ma resolved KYLIN-2021. --- Resolution: Fixed Fix Version/s: v1.6.0 > Cognos Issues > - > > Key: KYLIN-2021 > URL: https://issues.apache.org/jira/browse/KYLIN-2021 > Project: Kylin > Issue Type: Improvement >Reporter: hongbin ma >Assignee: hongbin ma > Fix For: v1.6.0 > > > cognos will generate some queries that kylin does not support yet -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KYLIN-2180) Add project config and make config priority become "cube > project > server"
[ https://issues.apache.org/jira/browse/KYLIN-2180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15739634#comment-15739634 ] kangkaisen commented on KYLIN-2180: --- HI, [~liyang.g...@gmail.com]. The commit c31c8490b05 has a issue: rename the attribute to "override_kylin_properties" will make front-end get the project override_kylin_properties failed. I fixed this issued and refactored the `ProjectRequest` at the same time. Please you review the patch, Thank you. > Add project config and make config priority become "cube > project > server" > > > Key: KYLIN-2180 > URL: https://issues.apache.org/jira/browse/KYLIN-2180 > Project: Kylin > Issue Type: New Feature > Components: Metadata >Affects Versions: v1.5.4.1 >Reporter: kangkaisen >Assignee: kangkaisen > Fix For: v1.6.1 > > Attachments: KYLIN-2180-tmp.patch, KYLIN-2180.patch > > > There are cases we want to override global kylin.properties in the scope of a > project. E.g. the queue name of Hadoop job. > Finally, the config priority for Kylin should be "cube > project > server". I > think which is reasonable. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KYLIN-2180) Add project config and make config priority become "cube > project > server"
[ https://issues.apache.org/jira/browse/KYLIN-2180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kangkaisen updated KYLIN-2180: -- Attachment: KYLIN-2180-refactor-ProjectRequest.patch This patch fix bug in c31c8490b05. > Add project config and make config priority become "cube > project > server" > > > Key: KYLIN-2180 > URL: https://issues.apache.org/jira/browse/KYLIN-2180 > Project: Kylin > Issue Type: New Feature > Components: Metadata >Affects Versions: v1.5.4.1 >Reporter: kangkaisen >Assignee: kangkaisen > Fix For: v1.6.1 > > Attachments: KYLIN-2180-refactor-ProjectRequest.patch, > KYLIN-2180-tmp.patch, KYLIN-2180.patch > > > There are cases we want to override global kylin.properties in the scope of a > project. E.g. the queue name of Hadoop job. > Finally, the config priority for Kylin should be "cube > project > server". I > think which is reasonable. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KYLIN-2262) Get "null" error when trigger a build with wrong cube name
[
https://issues.apache.org/jira/browse/KYLIN-2262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15739665#comment-15739665
]
QiLiFei commented on KYLIN-2262:
I do not understand what you said completely . Do you mean you reproduced this
issue using Kylin1.6 + Kafka0.9 ? So in this scenario when will you
release the next version kylin to fix the issue ? On the other hand ,
according to your official doc , it should be work correctly for the
Kylin1.6+Kafka,right ??? I'll try in this way to verify it tomorrow and then
get the feedback for u ! Thanks!
> Get "null" error when trigger a build with wrong cube name
> --
>
> Key: KYLIN-2262
> URL: https://issues.apache.org/jira/browse/KYLIN-2262
> Project: Kylin
> Issue Type: Bug
> Components: Client - CLI
>Affects Versions: v1.6.0
> Environment: CDH1.5.7
> Kylin1.6
> KAFKA-2.0.2-1.2.0.2.p0.5
>Reporter: QiLiFei
>Assignee: Shaofeng SHI
>Priority: Minor
> Fix For: v1.6.1
>
> Attachments: kylin.logError.txt
>
>
> When I build the kafka stream cube according to the doc
> (http://kylin.apache.org/docs16/tutorial/cube_streaming.html) , it always
> raise the error in the CLI
> {"url":"http://172.31.18.12:7070/kylin/api/cubes/StreamingCube9/build2","exception":null}
> From the kylin.log, there are only "Java.lang.NullPointerException"
> present!!I'm not sure what exactly happened there !!!Please give me some
> support !
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (KYLIN-2262) Get "null" error when trigger a build with wrong cube name
[
https://issues.apache.org/jira/browse/KYLIN-2262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15739679#comment-15739679
]
Shaofeng SHI commented on KYLIN-2262:
-
As I mentioned above, Kafka 0.10 is a prerequisite, 0.9 isn't supported. (This
is another topic, if you want to discuss it, please raise another thread in
mailing list)
My statements is for the original error you provided, the error trace in your
attachement. Please double check your cube name used in the origin URL:
"StreamingCube9"
> Get "null" error when trigger a build with wrong cube name
> --
>
> Key: KYLIN-2262
> URL: https://issues.apache.org/jira/browse/KYLIN-2262
> Project: Kylin
> Issue Type: Bug
> Components: Client - CLI
>Affects Versions: v1.6.0
> Environment: CDH1.5.7
> Kylin1.6
> KAFKA-2.0.2-1.2.0.2.p0.5
>Reporter: QiLiFei
>Assignee: Shaofeng SHI
>Priority: Minor
> Fix For: v1.6.1
>
> Attachments: kylin.logError.txt
>
>
> When I build the kafka stream cube according to the doc
> (http://kylin.apache.org/docs16/tutorial/cube_streaming.html) , it always
> raise the error in the CLI
> {"url":"http://172.31.18.12:7070/kylin/api/cubes/StreamingCube9/build2","exception":null}
> From the kylin.log, there are only "Java.lang.NullPointerException"
> present!!I'm not sure what exactly happened there !!!Please give me some
> support !
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (KYLIN-2266) Reduce memory usage for building global dict
kangkaisen created KYLIN-2266: - Summary: Reduce memory usage for building global dict Key: KYLIN-2266 URL: https://issues.apache.org/jira/browse/KYLIN-2266 Project: Kylin Issue Type: Improvement Affects Versions: v1.6.0 Reporter: kangkaisen Assignee: kangkaisen Because the input for building global dict is sequential，so we could set max cache size to 1 to reduce the memory usage. Although we also could set `kylin.dict.append.cache.size` to 1 to reduce the memory usage, most of users don't know this config. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KYLIN-2267) When FK/PK column type mismatched, get error on query: "NullPointerException: Column ### does not exist in row key desc"
Shaofeng SHI created KYLIN-2267:
---
Summary: When FK/PK column type mismatched, get error on query:
"NullPointerException: Column ### does not exist in row key desc"
Key: KYLIN-2267
URL: https://issues.apache.org/jira/browse/KYLIN-2267
Project: Kylin
Issue Type: Bug
Components: Query Engine
Reporter: Shaofeng SHI
Priority: Minor
I got this error in a cube which has one fact table and one lookup table; All
dimensions are normal, which looks be a very simple case (and the FK column
does exist on rowkey descriptor), but I got this error on every query that uses
columns on the lookup table; The error log is as below:
{code}
2016-12-08 13:58:25,177 INFO [http-bio-7070-exec-5] routing.QueryRouter:72 :
The realizations remaining: [his_realtime_cube_v7(CUBE)] And the final chosen
one is the first one
2016-12-08 13:58:25,219 DEBUG [http-bio-7070-exec-5]
enumerator.OLAPEnumerator:100 : query storage...
2016-12-08 13:58:25,220 ERROR [http-bio-7070-exec-5]
controller.QueryController:208 : Exception when execute sql
java.sql.SQLException: Error while executing SQL "select count(*) as "m0" from
"DEFAULT"."HIS_REALTIME" as "HIS_REALTIME" join
"DEFAULT"."V_STKCODE_INDUSTRYINFO2" as "V_STKCODE_INDUSTRYINFO2" on
"HIS_REALTIME"."STOCK_CODE" = "V_STKCODE_INDUSTRYINFO2"."STK_CODE"
LIMIT 5": Column DEFAULT.V_STKCODE_INDUSTRYINFO2.STK_CODE does not exist in
row key desc
at org.apache.calcite.avatica.Helper.createException(Helper.java:56)
at org.apache.calcite.avatica.Helper.createException(Helper.java:41)
at
org.apache.calcite.avatica.AvaticaStatement.executeInternal(AvaticaStatement.java:147)
at
org.apache.calcite.avatica.AvaticaStatement.executeQuery(AvaticaStatement.java:208)
at
org.apache.kylin.rest.service.QueryService.execute(QueryService.java:407)
at
org.apache.kylin.rest.service.QueryService.queryWithSqlMassage(QueryService.java:321)
at
org.apache.kylin.rest.service.QueryService.query(QueryService.java:128)
at
org.apache.kylin.rest.controller.QueryController.doQueryWithCache(QueryController.java:191)
at
org.apache.kylin.rest.controller.QueryController.query(QueryController.java:94)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
org.springframework.web.method.support.InvocableHandlerMethod.doInvoke(InvocableHandlerMethod.java:221)
at
org.springframework.web.method.support.InvocableHandlerMethod.invokeForRequest(InvocableHandlerMethod.java:136)
at
org.springframework.web.servlet.mvc.method.annotation.ServletInvocableHandlerMethod.invokeAndHandle(ServletInvocableHandlerMethod.java:104)
at
org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.invokeHandleMethod(RequestMappingHandlerAdapter.java:743)
at
org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.handleInternal(RequestMappingHandlerAdapter.java:672)
at
org.springframework.web.servlet.mvc.method.AbstractHandlerMethodAdapter.handle(AbstractHandlerMethodAdapter.java:82)
at
org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:933)
at
org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:867)
at
org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:951)
at
org.springframework.web.servlet.FrameworkServlet.doPost(FrameworkServlet.java:853)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:650)
at
org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:827)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at
org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:330)
at
org.springframework.security.web.access.intercept.FilterSecurityInterceptor.invoke(FilterSecurityInterceptor.java:118)
at
org.springframework.security.web.access.intercept.FilterSecurityInterceptor.doFilter(FilterSecurityIntercepto
[jira] [Updated] (KYLIN-2266) Reduce memory usage for building global dict
[ https://issues.apache.org/jira/browse/KYLIN-2266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kangkaisen updated KYLIN-2266: -- Attachment: KYLIN-2266.patch This is the patch > Reduce memory usage for building global dict > > > Key: KYLIN-2266 > URL: https://issues.apache.org/jira/browse/KYLIN-2266 > Project: Kylin > Issue Type: Improvement >Affects Versions: v1.6.0 >Reporter: kangkaisen >Assignee: kangkaisen > Attachments: KYLIN-2266.patch > > > Because the input for building global dict is sequential，so we could set max > cache size to 1 to reduce the memory usage. > Although we also could set `kylin.dict.append.cache.size` to 1 to reduce the > memory usage, most of users don't know this config. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KYLIN-2267) When FK/PK column type mismatched, get error on query: "NullPointerException: Column ### does not exist in row key desc"
[
https://issues.apache.org/jira/browse/KYLIN-2267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shaofeng SHI updated KYLIN-2267:
Description:
I got this error in a cube which has one fact table and one lookup table; All
dimensions are normal, which looks be a very simple case (and the FK column
does exist on rowkey descriptor), but I got this error on every query that uses
columns on the lookup table; The error log is as below:
{code}
2016-12-08 13:58:25,177 INFO [http-bio-7070-exec-5] routing.QueryRouter:72 :
The realizations remaining: [his_realtime_cube_v7(CUBE)] And the final chosen
one is the first one
2016-12-08 13:58:25,219 DEBUG [http-bio-7070-exec-5]
enumerator.OLAPEnumerator:100 : query storage...
2016-12-08 13:58:25,220 ERROR [http-bio-7070-exec-5]
controller.QueryController:208 : Exception when execute sql
java.sql.SQLException: Error while executing SQL "select count(*) as "m0" from
"DEFAULT"."HIS_REALTIME" as "HIS_REALTIME" join
"DEFAULT"."V_STKCODE_INDUSTRYINFO2" as "V_STKCODE_INDUSTRYINFO2" on
"HIS_REALTIME"."STOCK_CODE" = "V_STKCODE_INDUSTRYINFO2"."STK_CODE"
LIMIT 5": Column DEFAULT.V_STKCODE_INDUSTRYINFO2.STK_CODE does not exist in
row key desc
at org.apache.calcite.avatica.Helper.createException(Helper.java:56)
at org.apache.calcite.avatica.Helper.createException(Helper.java:41)
at
org.apache.calcite.avatica.AvaticaStatement.executeInternal(AvaticaStatement.java:147)
at
org.apache.calcite.avatica.AvaticaStatement.executeQuery(AvaticaStatement.java:208)
at
org.apache.kylin.rest.service.QueryService.execute(QueryService.java:407)
at
org.apache.kylin.rest.service.QueryService.queryWithSqlMassage(QueryService.java:321)
at
org.apache.kylin.rest.service.QueryService.query(QueryService.java:128)
at
org.apache.kylin.rest.controller.QueryController.doQueryWithCache(QueryController.java:191)
at
org.apache.kylin.rest.controller.QueryController.query(QueryController.java:94)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
org.springframework.web.method.support.InvocableHandlerMethod.doInvoke(InvocableHandlerMethod.java:221)
at
org.springframework.web.method.support.InvocableHandlerMethod.invokeForRequest(InvocableHandlerMethod.java:136)
at
org.springframework.web.servlet.mvc.method.annotation.ServletInvocableHandlerMethod.invokeAndHandle(ServletInvocableHandlerMethod.java:104)
at
org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.invokeHandleMethod(RequestMappingHandlerAdapter.java:743)
at
org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.handleInternal(RequestMappingHandlerAdapter.java:672)
at
org.springframework.web.servlet.mvc.method.AbstractHandlerMethodAdapter.handle(AbstractHandlerMethodAdapter.java:82)
at
org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:933)
at
org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:867)
at
org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:951)
at
org.springframework.web.servlet.FrameworkServlet.doPost(FrameworkServlet.java:853)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:650)
at
org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:827)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at
org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:330)
at
org.springframework.security.web.access.intercept.FilterSecurityInterceptor.invoke(FilterSecurityInterceptor.java:118)
at
org.springframework.security.web.access.intercept.FilterSecurityInterceptor.doFilter(FilterSecurityInterceptor.java:84)
at
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342)
at
org.springframework.security.web.access.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:113)
[jira] [Updated] (KYLIN-2267) When FK/PK column type mismatched, get error on query: "NullPointerException: Column ### does not exist in row key desc"
[
https://issues.apache.org/jira/browse/KYLIN-2267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shaofeng SHI updated KYLIN-2267:
Description:
I got this error in a cube which has one fact table and one lookup table; All
dimensions are normal, which looks be a very simple case (and the FK column
does exist on rowkey descriptor), but I got this error on every query that uses
columns on the lookup table; The error log is as below:
{code}
2016-12-08 13:58:25,177 INFO [http-bio-7070-exec-5] routing.QueryRouter:72 :
The realizations remaining: [his_realtime_cube_v7(CUBE)] And the final chosen
one is the first one
2016-12-08 13:58:25,219 DEBUG [http-bio-7070-exec-5]
enumerator.OLAPEnumerator:100 : query storage...
2016-12-08 13:58:25,220 ERROR [http-bio-7070-exec-5]
controller.QueryController:208 : Exception when execute sql
java.sql.SQLException: Error while executing SQL "select count(*) as "m0" from
"DEFAULT"."HIS_REALTIME" as "HIS_REALTIME" join
"DEFAULT"."V_STKCODE_INDUSTRYINFO2" as "V_STKCODE_INDUSTRYINFO2" on
"HIS_REALTIME"."STOCK_CODE" = "V_STKCODE_INDUSTRYINFO2"."STK_CODE"
LIMIT 5": Column DEFAULT.V_STKCODE_INDUSTRYINFO2.STK_CODE does not exist in
row key desc
at org.apache.calcite.avatica.Helper.createException(Helper.java:56)
at org.apache.calcite.avatica.Helper.createException(Helper.java:41)
at
org.apache.calcite.avatica.AvaticaStatement.executeInternal(AvaticaStatement.java:147)
at
org.apache.calcite.avatica.AvaticaStatement.executeQuery(AvaticaStatement.java:208)
at
org.apache.kylin.rest.service.QueryService.execute(QueryService.java:407)
at
org.apache.kylin.rest.service.QueryService.queryWithSqlMassage(QueryService.java:321)
at
org.apache.kylin.rest.service.QueryService.query(QueryService.java:128)
at
org.apache.kylin.rest.controller.QueryController.doQueryWithCache(QueryController.java:191)
at
org.apache.kylin.rest.controller.QueryController.query(QueryController.java:94)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
org.springframework.web.method.support.InvocableHandlerMethod.doInvoke(InvocableHandlerMethod.java:221)
at
org.springframework.web.method.support.InvocableHandlerMethod.invokeForRequest(InvocableHandlerMethod.java:136)
at
org.springframework.web.servlet.mvc.method.annotation.ServletInvocableHandlerMethod.invokeAndHandle(ServletInvocableHandlerMethod.java:104)
at
org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.invokeHandleMethod(RequestMappingHandlerAdapter.java:743)
at
org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.handleInternal(RequestMappingHandlerAdapter.java:672)
at
org.springframework.web.servlet.mvc.method.AbstractHandlerMethodAdapter.handle(AbstractHandlerMethodAdapter.java:82)
at
org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:933)
at
org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:867)
at
org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:951)
at
org.springframework.web.servlet.FrameworkServlet.doPost(FrameworkServlet.java:853)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:650)
at
org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:827)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at
org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:330)
at
org.springframework.security.web.access.intercept.FilterSecurityInterceptor.invoke(FilterSecurityInterceptor.java:118)
at
org.springframework.security.web.access.intercept.FilterSecurityInterceptor.doFilter(FilterSecurityInterceptor.java:84)
at
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342)
at
org.springframework.security.web.access.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:113)
[jira] [Updated] (KYLIN-2239) Remove refresh buildType
[ https://issues.apache.org/jira/browse/KYLIN-2239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kangkaisen updated KYLIN-2239: -- Summary: Remove refresh buildType (was: Remove refreshSegment in JobService) > Remove refresh buildType > > > Key: KYLIN-2239 > URL: https://issues.apache.org/jira/browse/KYLIN-2239 > Project: Kylin > Issue Type: Improvement >Reporter: kangkaisen >Assignee: kangkaisen >Priority: Minor > > currently, we have three build types：build, refresh, merge. But the build > and the refresh type only is one job type indeed and the build type could > replace the refresh type completely. > So, I think the refresh type is redundant. we can firstly remove > refreshSegment in JobService internal and keep the web api unchanged. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KYLIN-2239) Remove refresh buildType
[ https://issues.apache.org/jira/browse/KYLIN-2239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15739755#comment-15739755 ] Shaofeng SHI commented on KYLIN-2239: - I think "build" and "refresh" are still have difference in the scenario: one is to build new data, the other is to build history data. The checks for them are different; Besides, in the streaming case, the input for these two types are different: for "build", user need to specify the partition-specific offsets (unless using the reserved "0" and Long.MAX_VALUE); for "refresh", user only need specify the summed offsets. > Remove refresh buildType > > > Key: KYLIN-2239 > URL: https://issues.apache.org/jira/browse/KYLIN-2239 > Project: Kylin > Issue Type: Improvement >Reporter: kangkaisen >Assignee: kangkaisen >Priority: Minor > > currently, we have three build types：build, refresh, merge. But the build > and the refresh type only is one job type indeed and the build type could > replace the refresh type completely. > So, I think the refresh type is redundant. we can firstly remove > refreshSegment in JobService internal and keep the web api unchanged. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (KYLIN-2239) Remove refresh buildType
[ https://issues.apache.org/jira/browse/KYLIN-2239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15739755#comment-15739755 ] Shaofeng SHI edited comment on KYLIN-2239 at 12/11/16 1:42 PM: --- I think "build" and "refresh" still have difference in the scenarios: one is to build new data, the other is to build history data. The checks for them are different; Besides, in the streaming case, the input for these two types are different: for "build", user need to specify the partition-specific offsets (unless using the reserved "0" and Long.MAX_VALUE); for "refresh", user only need specify the summed offsets. was (Author: shaofengshi): I think "build" and "refresh" are still have difference in the scenario: one is to build new data, the other is to build history data. The checks for them are different; Besides, in the streaming case, the input for these two types are different: for "build", user need to specify the partition-specific offsets (unless using the reserved "0" and Long.MAX_VALUE); for "refresh", user only need specify the summed offsets. > Remove refresh buildType > > > Key: KYLIN-2239 > URL: https://issues.apache.org/jira/browse/KYLIN-2239 > Project: Kylin > Issue Type: Improvement >Reporter: kangkaisen >Assignee: kangkaisen >Priority: Minor > > currently, we have three build types：build, refresh, merge. But the build > and the refresh type only is one job type indeed and the build type could > replace the refresh type completely. > So, I think the refresh type is redundant. we can firstly remove > refreshSegment in JobService internal and keep the web api unchanged. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KYLIN-2239) Remove refresh buildType
[ https://issues.apache.org/jira/browse/KYLIN-2239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15739793#comment-15739793 ] kangkaisen commented on KYLIN-2239: --- Hi, Shaofeng. 1 The "refresh" buildType only could build existing one segment not whole history data or multiple segments. I think which doesn't match the "refresh" semantic completely. Besides, the "build" type could replace the "refresh" type completely. 2 for the streaming case, whether we only need do some change in web ui? I think which isn't buildType issue. If I think wrong, please correct me. thanks. > Remove refresh buildType > > > Key: KYLIN-2239 > URL: https://issues.apache.org/jira/browse/KYLIN-2239 > Project: Kylin > Issue Type: Improvement >Reporter: kangkaisen >Assignee: kangkaisen >Priority: Minor > > currently, we have three build types：build, refresh, merge. But the build > and the refresh type only is one job type indeed and the build type could > replace the refresh type completely. > So, I think the refresh type is redundant. we can firstly remove > refreshSegment in JobService internal and keep the web api unchanged. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KYLIN-2021) Cognos Issues
[ https://issues.apache.org/jira/browse/KYLIN-2021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15739838#comment-15739838 ] Billy Liu commented on KYLIN-2021: -- Hi [~mahongbin], could you explain more what the issues are? Especially the issue topic name. Then we could send out more clear message to Cognos community how Kylin could support, and what not support yet. > Cognos Issues > - > > Key: KYLIN-2021 > URL: https://issues.apache.org/jira/browse/KYLIN-2021 > Project: Kylin > Issue Type: Improvement >Reporter: hongbin ma >Assignee: hongbin ma > Fix For: v1.6.0 > > > cognos will generate some queries that kylin does not support yet -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KYLIN-2239) Remove refresh buildType
[ https://issues.apache.org/jira/browse/KYLIN-2239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15739837#comment-15739837 ] Shaofeng SHI commented on KYLIN-2239: - Kaisen, actually refresh multiple segments at once is supported I rember: specify the startOffset as the first segment's start, and endOffset as the last segment's end; The only limitation is the web GUI hasn't been updated, but it should be easy to change. For streaming case, the Web GUI has been updated for both build and refresh; Separating "new" and "history" build makes the logic more clear than combine them together; ,what's the problem you see with as-is design? > Remove refresh buildType > > > Key: KYLIN-2239 > URL: https://issues.apache.org/jira/browse/KYLIN-2239 > Project: Kylin > Issue Type: Improvement >Reporter: kangkaisen >Assignee: kangkaisen >Priority: Minor > > currently, we have three build types：build, refresh, merge. But the build > and the refresh type only is one job type indeed and the build type could > replace the refresh type completely. > So, I think the refresh type is redundant. we can firstly remove > refreshSegment in JobService internal and keep the web api unchanged. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KYLIN-2144) move useful operation tools to org.apache.kylin.tool
[ https://issues.apache.org/jira/browse/KYLIN-2144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15739841#comment-15739841 ] Shaofeng SHI commented on KYLIN-2144: - Okay it is good; we can remove the deprecated later and also update the doc within the new version. Thanks hongbin. > move useful operation tools to org.apache.kylin.tool > > > Key: KYLIN-2144 > URL: https://issues.apache.org/jira/browse/KYLIN-2144 > Project: Kylin > Issue Type: Improvement >Reporter: hongbin ma >Assignee: hongbin ma > Fix For: v1.6.1 > > > due to historical reasons, the following 5 operation tools: > StorageCleanupJob,MetadataCleanupJob,CubeMigrationCLI, > CubeMigrationCheckCLI,ExtendCubeToHybridCLI > locates in org.apache.kylin.storage.hbase.util, which brings dependency > issues and other concerns. > In 1.6.1 and later, we'll move the 5 tools to org.apache.kylin.tool. The old > java class will mark as deprecated, and no longer under maintainance. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KYLIN-2031) New Fix_length_Hex encoding to support hash value and better Integer encoding to support negative value
[ https://issues.apache.org/jira/browse/KYLIN-2031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Billy Liu updated KYLIN-2031: - Summary: New Fix_length_Hex encoding to support hash value and better Integer encoding to support negative value (was: some more DimensionEncoding) > New Fix_length_Hex encoding to support hash value and better Integer encoding > to support negative value > --- > > Key: KYLIN-2031 > URL: https://issues.apache.org/jira/browse/KYLIN-2031 > Project: Kylin > Issue Type: New Feature >Reporter: hongbin ma >Assignee: hongbin ma > Fix For: v1.6.1 > > > 1. for some use cases string value represent hash code is used. The string > only consist of [0~9A~F] (hex values), so two characters can be squashed into > one byte > 2. The current IntegerDimEnc does not support negative values, need another > IntegerDimEnc that supports negative values -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KYLIN-2266) Reduce memory usage for building global dict
[ https://issues.apache.org/jira/browse/KYLIN-2266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15739860#comment-15739860 ] Dayue Gao commented on KYLIN-2266: -- A better way would be refine AppendTrieDictionary to get rid of CachedTreeMap in build path. This could reduce code complexity substantially. > Reduce memory usage for building global dict > > > Key: KYLIN-2266 > URL: https://issues.apache.org/jira/browse/KYLIN-2266 > Project: Kylin > Issue Type: Improvement >Affects Versions: v1.6.0 >Reporter: kangkaisen >Assignee: kangkaisen > Attachments: KYLIN-2266.patch > > > Because the input for building global dict is sequential，so we could set max > cache size to 1 to reduce the memory usage. > Although we also could set `kylin.dict.append.cache.size` to 1 to reduce the > memory usage, most of users don't know this config. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KYLIN-2265) Adjust default config for resource-limit sandbox
[ https://issues.apache.org/jira/browse/KYLIN-2265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15739871#comment-15739871 ] Shaofeng SHI commented on KYLIN-2265: - My opinion is in the released binary package, the configuration should be the default (recommended) configurations, not minimal nor maximal; because most users won't change them unless they got issue; Having a document to explain these parameters is a good approach, then users will have ways to customize. > Adjust default config for resource-limit sandbox > > > Key: KYLIN-2265 > URL: https://issues.apache.org/jira/browse/KYLIN-2265 > Project: Kylin > Issue Type: Improvement > Components: General >Affects Versions: v1.6.0 >Reporter: Billy Liu >Assignee: Billy Liu > Attachments: KYLIN-2265.patch > > > Most users deploy Kylin on their own sandbox for the first trial. Most > sandbox has most 8G memory. The most used sandboxes are HDP sandbox and CDH > sandbox. We'd better make the default kylin configuration convenient for > these sandbox environment. The suggestion includes reducing region-cut-gb, > hfile-size-gb, max-region-count, reduce-input-mb, > max-reducer-number,mapreduce.map.memory.mb,mapreduce.map.java.opts. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KYLIN-2265) Adjust default config for resource-limit sandbox
[ https://issues.apache.org/jira/browse/KYLIN-2265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15739885#comment-15739885 ] Billy Liu commented on KYLIN-2265: -- Hi Shaofeng, do you have more suggestions on what the default would be. I try to propose the sandbox(10G memory, 2 core) as default, because it has the least limitations to the hadoop environment. The default configuration should build sample cube smoothly. For production deployment, the administrator should reconsider the cluster size, and source data size carefully. The configuration document is mandatory for reference. > Adjust default config for resource-limit sandbox > > > Key: KYLIN-2265 > URL: https://issues.apache.org/jira/browse/KYLIN-2265 > Project: Kylin > Issue Type: Improvement > Components: General >Affects Versions: v1.6.0 >Reporter: Billy Liu >Assignee: Billy Liu > Attachments: KYLIN-2265.patch > > > Most users deploy Kylin on their own sandbox for the first trial. Most > sandbox has most 8G memory. The most used sandboxes are HDP sandbox and CDH > sandbox. We'd better make the default kylin configuration convenient for > these sandbox environment. The suggestion includes reducing region-cut-gb, > hfile-size-gb, max-region-count, reduce-input-mb, > max-reducer-number,mapreduce.map.memory.mb,mapreduce.map.java.opts. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KYLIN-2268) Potential NPE in ModelDimensionDesc#init()
Ted Yu created KYLIN-2268:
-
Summary: Potential NPE in ModelDimensionDesc#init()
Key: KYLIN-2268
URL: https://issues.apache.org/jira/browse/KYLIN-2268
Project: Kylin
Issue Type: Bug
Reporter: Ted Yu
Priority: Minor
{code}
if (columns != null) {
StringUtil.toUpperCaseArray(columns, columns);
}
if (model != null) {
table = model.findTable(table).getAlias();
for (int i = 0; i < columns.length; i++) {
{code}
In the second if block, columns is accessed without null check.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (KYLIN-2239) Remove refresh buildType
[ https://issues.apache.org/jira/browse/KYLIN-2239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15740760#comment-15740760 ] kangkaisen commented on KYLIN-2239: --- Hi, Shaofeng. 1. you are right that refresh multiple segments at once is supported, I remembered wrong. 2. I agree with you that separating "new" and "history" build makes the logic more clear than combine them together. But actually the "build" type can do anything and it's function contains the "refresh". 3. I think we can keep "refresh" tag in Web GUI for users to refresh "history" data and "build" tag to build "new" data, but we both use "build" type actually. 4. I want to remove the "refresh" type , because when I wrote scheduler script to build production cube in my company, I found the "refresh" type is useless and I realized all demand only with "build" type. 5 This is not a important issue and it doesn't affect common user. If you think the "refresh" type is necessary，I could close the issue. > Remove refresh buildType > > > Key: KYLIN-2239 > URL: https://issues.apache.org/jira/browse/KYLIN-2239 > Project: Kylin > Issue Type: Improvement >Reporter: kangkaisen >Assignee: kangkaisen >Priority: Minor > > currently, we have three build types：build, refresh, merge. But the build > and the refresh type only is one job type indeed and the build type could > replace the refresh type completely. > So, I think the refresh type is redundant. we can firstly remove > refreshSegment in JobService internal and keep the web api unchanged. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KYLIN-2266) Reduce memory usage for building global dict
[
https://issues.apache.org/jira/browse/KYLIN-2266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15740788#comment-15740788
]
kangkaisen commented on KYLIN-2266:
---
I agree with you.
But before we refactor {{AppendTrieDictionary}} and {{CachedTreeMap}}, this
patch is the most direct and simple way to reduce the memory usage
significantly.
> Reduce memory usage for building global dict
>
>
> Key: KYLIN-2266
> URL: https://issues.apache.org/jira/browse/KYLIN-2266
> Project: Kylin
> Issue Type: Improvement
>Affects Versions: v1.6.0
>Reporter: kangkaisen
>Assignee: kangkaisen
> Attachments: KYLIN-2266.patch
>
>
> Because the input for building global dict is sequential，so we could set max
> cache size to 1 to reduce the memory usage.
> Although we also could set `kylin.dict.append.cache.size` to 1 to reduce the
> memory usage, most of users don't know this config.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (KYLIN-2239) Remove refresh buildType
[ https://issues.apache.org/jira/browse/KYLIN-2239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15740795#comment-15740795 ] Shaofeng SHI commented on KYLIN-2239: - Hi Kaisen, >From API point of view, I want to keep it as stable as possible; even to >change, still need consider the backward compitable; So I suggest keep it; >Maybe someday Kylin will extend here, the current design keeps flexibility. So far for the scheduler script, you can use the "build" type for both history and new data; > Remove refresh buildType > > > Key: KYLIN-2239 > URL: https://issues.apache.org/jira/browse/KYLIN-2239 > Project: Kylin > Issue Type: Improvement >Reporter: kangkaisen >Assignee: kangkaisen >Priority: Minor > > currently, we have three build types：build, refresh, merge. But the build > and the refresh type only is one job type indeed and the build type could > replace the refresh type completely. > So, I think the refresh type is redundant. we can firstly remove > refreshSegment in JobService internal and keep the web api unchanged. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KYLIN-2262) Get "null" error when trigger a build with wrong cube name
[
https://issues.apache.org/jira/browse/KYLIN-2262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15740805#comment-15740805
]
QiLiFei commented on KYLIN-2262:
I'm not exactly sure the "StreamingCube9" exist or not when I submit the curl
command currently because I've removed some test cubes. And currently it always
raises the "java.lang.NoSuchMethodError:
org.apache.kafka.clients.consumer.KafkaConsumer.assign(Ljava/util/Collection;"
error as we discussed before.
And when I try to install the kafka1.0 on CDH5.7.2 , seems the kafka cannot be
actived successfully! From the
"http://archive.cloudera.com/kafka/parcels/2.0.2.5/manifest.json " you can know
that only kafka0.9.0 is supported instead of kafka1.0!!!
Let's summarize my question:
1.Verison : CDH5.7.2 + kafka_2.11-0.9.0-kafka-2.0.2.jar
We've made sure that it cannot support Kylin1.6 streaming cube
(Incremental)build by this kafka version.
2.I'm not sure currently whether latest version kafka can be supported for CDH
Cluster . Could you please provide a download link for the integrated CDH Kafka
such as "kafka_2.11-0.10.0-kafka-2.0.2.jar" ?
3.If there is no the integrated CDH Kafka , could you please provide the
download link for the latest Apache kafka package ?
> Get "null" error when trigger a build with wrong cube name
> --
>
> Key: KYLIN-2262
> URL: https://issues.apache.org/jira/browse/KYLIN-2262
> Project: Kylin
> Issue Type: Bug
> Components: Client - CLI
>Affects Versions: v1.6.0
> Environment: CDH1.5.7
> Kylin1.6
> KAFKA-2.0.2-1.2.0.2.p0.5
>Reporter: QiLiFei
>Assignee: Shaofeng SHI
>Priority: Minor
> Fix For: v1.6.1
>
> Attachments: kylin.logError.txt
>
>
> When I build the kafka stream cube according to the doc
> (http://kylin.apache.org/docs16/tutorial/cube_streaming.html) , it always
> raise the error in the CLI
> {"url":"http://172.31.18.12:7070/kylin/api/cubes/StreamingCube9/build2","exception":null}
> From the kylin.log, there are only "Java.lang.NullPointerException"
> present!!I'm not sure what exactly happened there !!!Please give me some
> support !
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (KYLIN-2266) Reduce memory usage for building global dict
[ https://issues.apache.org/jira/browse/KYLIN-2266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15740819#comment-15740819 ] Shaofeng SHI commented on KYLIN-2266: - Merged in master branch; thanks kaisen! > Reduce memory usage for building global dict > > > Key: KYLIN-2266 > URL: https://issues.apache.org/jira/browse/KYLIN-2266 > Project: Kylin > Issue Type: Improvement >Affects Versions: v1.6.0 >Reporter: kangkaisen >Assignee: kangkaisen > Fix For: v1.6.1 > > Attachments: KYLIN-2266.patch > > > Because the input for building global dict is sequential，so we could set max > cache size to 1 to reduce the memory usage. > Although we also could set `kylin.dict.append.cache.size` to 1 to reduce the > memory usage, most of users don't know this config. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KYLIN-2266) Reduce memory usage for building global dict
[ https://issues.apache.org/jira/browse/KYLIN-2266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaofeng SHI updated KYLIN-2266: Fix Version/s: v1.6.1 > Reduce memory usage for building global dict > > > Key: KYLIN-2266 > URL: https://issues.apache.org/jira/browse/KYLIN-2266 > Project: Kylin > Issue Type: Improvement >Affects Versions: v1.6.0 >Reporter: kangkaisen >Assignee: kangkaisen > Fix For: v1.6.1 > > Attachments: KYLIN-2266.patch > > > Because the input for building global dict is sequential，so we could set max > cache size to 1 to reduce the memory usage. > Although we also could set `kylin.dict.append.cache.size` to 1 to reduce the > memory usage, most of users don't know this config. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KYLIN-2269) Reduce MR memory usage for global dict
kangkaisen created KYLIN-2269:
-
Summary: Reduce MR memory usage for global dict
Key: KYLIN-2269
URL: https://issues.apache.org/jira/browse/KYLIN-2269
Project: Kylin
Issue Type: Improvement
Affects Versions: v1.6.0
Reporter: kangkaisen
Assignee: kangkaisen
currently, in {{Build Base Cuboid Data}}, if user use the global dict and the
global dict size significantly larger the mapper memory size, the
{{CachedTreeMap}} will load all values as much as possible and the soft
references object will stick around for a while when GC, So which will make the
{{Build Base Cuboid Data}} mapper pause for a long time even could not finish.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (KYLIN-2270) Reduce MR memory usage for global dict
kangkaisen created KYLIN-2270:
-
Summary: Reduce MR memory usage for global dict
Key: KYLIN-2270
URL: https://issues.apache.org/jira/browse/KYLIN-2270
Project: Kylin
Issue Type: Improvement
Affects Versions: v1.6.0
Reporter: kangkaisen
Assignee: kangkaisen
currently, in {{Build Base Cuboid Data}}, if user use the global dict and the
global dict size significantly larger the mapper memory size, the
{{CachedTreeMap}} will load all values as much as possible and the soft
references object will stick around for a while when GC, So which will make the
{{Build Base Cuboid Data}} mapper pause for a long time even could not finish.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (KYLIN-2270) Reduce MR memory usage for global dict
[
https://issues.apache.org/jira/browse/KYLIN-2270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
kangkaisen closed KYLIN-2270.
-
Resolution: Duplicate
> Reduce MR memory usage for global dict
> --
>
> Key: KYLIN-2270
> URL: https://issues.apache.org/jira/browse/KYLIN-2270
> Project: Kylin
> Issue Type: Improvement
>Affects Versions: v1.6.0
>Reporter: kangkaisen
>Assignee: kangkaisen
>
> currently, in {{Build Base Cuboid Data}}, if user use the global dict and the
> global dict size significantly larger the mapper memory size, the
> {{CachedTreeMap}} will load all values as much as possible and the soft
> references object will stick around for a while when GC, So which will make
> the {{Build Base Cuboid Data}} mapper pause for a long time even could not
> finish.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (KYLIN-2271) Purge cube may delete building segments
Shaofeng SHI created KYLIN-2271: --- Summary: Purge cube may delete building segments Key: KYLIN-2271 URL: https://issues.apache.org/jira/browse/KYLIN-2271 Project: Kylin Issue Type: Bug Components: REST Service Reporter: Shaofeng SHI Assignee: Shaofeng SHI Priority: Minor Fix For: v1.6.1 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KYLIN-2271) Purge cube may delete building segments
[ https://issues.apache.org/jira/browse/KYLIN-2271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaofeng SHI updated KYLIN-2271: Description: The purge cube API didn't check whether there is building segment, which will delete all segments; Then the build engine will encounter unexpected NPE. Expected behavior: when there is building segment, don't allow purge; User need discard the building jobs and then do the purge. > Purge cube may delete building segments > --- > > Key: KYLIN-2271 > URL: https://issues.apache.org/jira/browse/KYLIN-2271 > Project: Kylin > Issue Type: Bug > Components: REST Service >Reporter: Shaofeng SHI >Assignee: Shaofeng SHI >Priority: Minor > Fix For: v1.6.1 > > > The purge cube API didn't check whether there is building segment, which will > delete all segments; Then the build engine will encounter unexpected NPE. > Expected behavior: when there is building segment, don't allow purge; User > need discard the building jobs and then do the purge. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (KYLIN-2271) Purge cube may delete building segments
[ https://issues.apache.org/jira/browse/KYLIN-2271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaofeng SHI resolved KYLIN-2271. - Resolution: Fixed > Purge cube may delete building segments > --- > > Key: KYLIN-2271 > URL: https://issues.apache.org/jira/browse/KYLIN-2271 > Project: Kylin > Issue Type: Bug > Components: REST Service >Reporter: Shaofeng SHI >Assignee: Shaofeng SHI >Priority: Minor > Fix For: v1.6.1 > > > The purge cube API didn't check whether there is building segment, which will > delete all segments; Then the build engine will encounter unexpected NPE. > Expected behavior: when there is building segment, don't allow purge; User > need discard the building jobs and then do the purge. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KYLIN-2269) Reduce MR memory usage for global dict
[
https://issues.apache.org/jira/browse/KYLIN-2269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15740954#comment-15740954
]
kangkaisen commented on KYLIN-2269:
---
To resolve the issue, we could use {{CLUSTER BY}} to make the the mapper input
of {{Build Base Cuboid Data}} is sequential. since the input is sequential, we
could only use default memory size for mapper to load the global dict slice in
turn.
Of course, this method could only handle one ultra high cardinality column
well. but which is most scenarios.
> Reduce MR memory usage for global dict
> --
>
> Key: KYLIN-2269
> URL: https://issues.apache.org/jira/browse/KYLIN-2269
> Project: Kylin
> Issue Type: Improvement
>Affects Versions: v1.6.0
>Reporter: kangkaisen
>Assignee: kangkaisen
>
> currently, in {{Build Base Cuboid Data}}, if user use the global dict and the
> global dict size significantly larger the mapper memory size, the
> {{CachedTreeMap}} will load all values as much as possible and the soft
> references object will stick around for a while when GC, So which will make
> the {{Build Base Cuboid Data}} mapper pause for a long time even could not
> finish.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KYLIN-2269) Reduce MR memory usage for global dict
[
https://issues.apache.org/jira/browse/KYLIN-2269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
kangkaisen updated KYLIN-2269:
--
Attachment: KYLIN-2269.patch
This is the patch.
This patch has run a some time in our production env. which could reduce the
MR memory usage and mapper running time of Base Cuboid for global dict
significantly.
> Reduce MR memory usage for global dict
> --
>
> Key: KYLIN-2269
> URL: https://issues.apache.org/jira/browse/KYLIN-2269
> Project: Kylin
> Issue Type: Improvement
>Affects Versions: v1.6.0
>Reporter: kangkaisen
>Assignee: kangkaisen
> Attachments: KYLIN-2269.patch
>
>
> currently, in {{Build Base Cuboid Data}}, if user use the global dict and the
> global dict size significantly larger the mapper memory size, the
> {{CachedTreeMap}} will load all values as much as possible and the soft
> references object will stick around for a while when GC, So which will make
> the {{Build Base Cuboid Data}} mapper pause for a long time even could not
> finish.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (KYLIN-2269) Reduce MR memory usage for global dict
[
https://issues.apache.org/jira/browse/KYLIN-2269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15741084#comment-15741084
]
kangkaisen commented on KYLIN-2269:
---
Hi, [~mahongbin].
please you review the patch when you have time, I am not sure this feature and
{{shardBy}} feature whether could be used at the same time. if no, I will add
the check. Thank you.
> Reduce MR memory usage for global dict
> --
>
> Key: KYLIN-2269
> URL: https://issues.apache.org/jira/browse/KYLIN-2269
> Project: Kylin
> Issue Type: Improvement
>Affects Versions: v1.6.0
>Reporter: kangkaisen
>Assignee: kangkaisen
> Attachments: KYLIN-2269.patch
>
>
> currently, in {{Build Base Cuboid Data}}, if user use the global dict and the
> global dict size significantly larger the mapper memory size, the
> {{CachedTreeMap}} will load all values as much as possible and the soft
> references object will stick around for a while when GC, So which will make
> the {{Build Base Cuboid Data}} mapper pause for a long time even could not
> finish.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (KYLIN-2244) "kylin.job.cuboid.size.memhungry.ratio" shouldn't be applied on measures like TopN
[ https://issues.apache.org/jira/browse/KYLIN-2244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15741102#comment-15741102 ] Shaofeng SHI commented on KYLIN-2244: - Deprecate "kylin.cube.size-estimate-memhungry-ratio" and add new "kylin.cube.size-estimate-countdistinct-ratio" (with default 0.05). When estimate the cuboid size, for count distinct measure (both HLL and Bitmap), use this ration. For dimension and other measure value, use the ordinary "kylin.cube.size-estimate-ratio" (default 0.25). > "kylin.job.cuboid.size.memhungry.ratio" shouldn't be applied on measures like > TopN > -- > > Key: KYLIN-2244 > URL: https://issues.apache.org/jira/browse/KYLIN-2244 > Project: Kylin > Issue Type: Improvement > Components: Job Engine >Reporter: Shaofeng SHI > Fix For: v1.6.1 > > > The parameter "kylin.job.cuboid.size.memhungry.ratio" (new name " > kylin.cube.size-estimate-memhungry-ratio") default value 0.05, is based on > the compression ration on HyperLogLog; it doesn't fit for other memory hungry > measures like TopN, Raw, etc; -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KYLIN-2244) "kylin.job.cuboid.size.memhungry.ratio" shouldn't be applied on measures like TopN
[ https://issues.apache.org/jira/browse/KYLIN-2244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaofeng SHI updated KYLIN-2244: Fix Version/s: v1.6.1 Component/s: Job Engine > "kylin.job.cuboid.size.memhungry.ratio" shouldn't be applied on measures like > TopN > -- > > Key: KYLIN-2244 > URL: https://issues.apache.org/jira/browse/KYLIN-2244 > Project: Kylin > Issue Type: Improvement > Components: Job Engine >Reporter: Shaofeng SHI >Assignee: Shaofeng SHI > Fix For: v1.6.1 > > > The parameter "kylin.job.cuboid.size.memhungry.ratio" (new name " > kylin.cube.size-estimate-memhungry-ratio") default value 0.05, is based on > the compression ration on HyperLogLog; it doesn't fit for other memory hungry > measures like TopN, Raw, etc; -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KYLIN-2249) Build cube error when use "inmem" but ok with "layer"
[ https://issues.apache.org/jira/browse/KYLIN-2249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15741147#comment-15741147 ] hoangle commented on KYLIN-2249: [~mahongbin] Can you look up my issue ? Thanks > Build cube error when use "inmem" but ok with "layer" > - > > Key: KYLIN-2249 > URL: https://issues.apache.org/jira/browse/KYLIN-2249 > Project: Kylin > Issue Type: Bug >Affects Versions: v1.6.0 > Environment: CentOS >Reporter: hoangle > Original Estimate: 410h > Remaining Estimate: 410h > > My cube building is ok if I set configure: > kylin.cube.algorithm=layer > But It always error (at Step Name: Build Cube) when I change "layer" to > "inmem" > > 2016-12-05 17:17:37,451 ERROR [Thread-13] > org.apache.kylin.dict.TrieDictionary: Not a valid value: 122594010041 > 2016-12-05 17:17:38,452 ERROR [pool-8-thread-1] > org.apache.kylin.cube.inmemcubing.DoggedCubeBuilder: Dogged Cube Build error > java.io.IOException: java.lang.IllegalArgumentException: Value not exists! > at > org.apache.kylin.cube.inmemcubing.DoggedCubeBuilder$BuildOnce.abort(DoggedCubeBuilder.java:196) > at > org.apache.kylin.cube.inmemcubing.DoggedCubeBuilder$BuildOnce.checkException(DoggedCubeBuilder.java:169) > at > org.apache.kylin.cube.inmemcubing.DoggedCubeBuilder$BuildOnce.build(DoggedCubeBuilder.java:116) > at > org.apache.kylin.cube.inmemcubing.DoggedCubeBuilder.build(DoggedCubeBuilder.java:75) > at > org.apache.kylin.cube.inmemcubing.AbstractInMemCubeBuilder$1.run(AbstractInMemCubeBuilder.java:82) > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > Caused by: java.lang.IllegalArgumentException: Value not exists! > at > org.apache.kylin.common.util.Dictionary.getIdFromValueBytes(Dictionary.java:162) > at > org.apache.kylin.dict.TrieDictionary.getIdFromValueImpl(TrieDictionary.java:167) > at > org.apache.kylin.common.util.Dictionary.getIdFromValue(Dictionary.java:98) > at > org.apache.kylin.dimension.DictionaryDimEnc$DictionarySerializer.serialize(DictionaryDimEnc.java:121) > at > org.apache.kylin.cube.gridtable.CubeCodeSystem.encodeColumnValue(CubeCodeSystem.java:121) > at > org.apache.kylin.cube.gridtable.CubeCodeSystem.encodeColumnValue(CubeCodeSystem.java:110) > at org.apache.kylin.gridtable.GTRecord.setValues(GTRecord.java:93) > at org.apache.kylin.gridtable.GTRecord.setValues(GTRecord.java:81) > at > org.apache.kylin.cube.inmemcubing.InMemCubeBuilderInputConverter.convert(InMemCubeBuilderInputConverter.java:74) > at > org.apache.kylin.cube.inmemcubing.InMemCubeBuilder$InputConverter$1.next(InMemCubeBuilder.java:544) > at > org.apache.kylin.cube.inmemcubing.InMemCubeBuilder$InputConverter$1.next(InMemCubeBuilder.java:525) > at > org.apache.kylin.gridtable.GTAggregateScanner.iterator(GTAggregateScanner.java:139) > at > org.apache.kylin.cube.inmemcubing.InMemCubeBuilder.createBaseCuboid(InMemCubeBuilder.java:341) > at > org.apache.kylin.cube.inmemcubing.InMemCubeBuilder.build(InMemCubeBuilder.java:168) > at > org.apache.kylin.cube.inmemcubing.InMemCubeBuilder.build(InMemCubeBuilder.java:137) > at > org.apache.kylin.cube.inmemcubing.DoggedCubeBuilder$SplitThread.run(DoggedCubeBuilder.java:284) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (KYLIN-2262) Get "null" error when trigger a build with wrong cube name
[
https://issues.apache.org/jira/browse/KYLIN-2262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
QiLiFei reopened KYLIN-2262:
Seems that there is no Kafka1.0 for the CDH available currently . Or maybe I
didn't find it . Please provide related download info as the latest comments.
Thanks a lot !!!
> Get "null" error when trigger a build with wrong cube name
> --
>
> Key: KYLIN-2262
> URL: https://issues.apache.org/jira/browse/KYLIN-2262
> Project: Kylin
> Issue Type: Bug
> Components: Client - CLI
>Affects Versions: v1.6.0
> Environment: CDH1.5.7
> Kylin1.6
> KAFKA-2.0.2-1.2.0.2.p0.5
>Reporter: QiLiFei
>Assignee: Shaofeng SHI
>Priority: Minor
> Fix For: v1.6.1
>
> Attachments: kylin.logError.txt
>
>
> When I build the kafka stream cube according to the doc
> (http://kylin.apache.org/docs16/tutorial/cube_streaming.html) , it always
> raise the error in the CLI
> {"url":"http://172.31.18.12:7070/kylin/api/cubes/StreamingCube9/build2","exception":null}
> From the kylin.log, there are only "Java.lang.NullPointerException"
> present!!I'm not sure what exactly happened there !!!Please give me some
> support !
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (KYLIN-2249) Build cube error when use "inmem" but ok with "layer"
[ https://issues.apache.org/jira/browse/KYLIN-2249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15741255#comment-15741255 ] Shaofeng SHI commented on KYLIN-2249: - please check KYLIN-2231 to see whether they're the same. > Build cube error when use "inmem" but ok with "layer" > - > > Key: KYLIN-2249 > URL: https://issues.apache.org/jira/browse/KYLIN-2249 > Project: Kylin > Issue Type: Bug >Affects Versions: v1.6.0 > Environment: CentOS >Reporter: hoangle > Original Estimate: 410h > Remaining Estimate: 410h > > My cube building is ok if I set configure: > kylin.cube.algorithm=layer > But It always error (at Step Name: Build Cube) when I change "layer" to > "inmem" > > 2016-12-05 17:17:37,451 ERROR [Thread-13] > org.apache.kylin.dict.TrieDictionary: Not a valid value: 122594010041 > 2016-12-05 17:17:38,452 ERROR [pool-8-thread-1] > org.apache.kylin.cube.inmemcubing.DoggedCubeBuilder: Dogged Cube Build error > java.io.IOException: java.lang.IllegalArgumentException: Value not exists! > at > org.apache.kylin.cube.inmemcubing.DoggedCubeBuilder$BuildOnce.abort(DoggedCubeBuilder.java:196) > at > org.apache.kylin.cube.inmemcubing.DoggedCubeBuilder$BuildOnce.checkException(DoggedCubeBuilder.java:169) > at > org.apache.kylin.cube.inmemcubing.DoggedCubeBuilder$BuildOnce.build(DoggedCubeBuilder.java:116) > at > org.apache.kylin.cube.inmemcubing.DoggedCubeBuilder.build(DoggedCubeBuilder.java:75) > at > org.apache.kylin.cube.inmemcubing.AbstractInMemCubeBuilder$1.run(AbstractInMemCubeBuilder.java:82) > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > Caused by: java.lang.IllegalArgumentException: Value not exists! > at > org.apache.kylin.common.util.Dictionary.getIdFromValueBytes(Dictionary.java:162) > at > org.apache.kylin.dict.TrieDictionary.getIdFromValueImpl(TrieDictionary.java:167) > at > org.apache.kylin.common.util.Dictionary.getIdFromValue(Dictionary.java:98) > at > org.apache.kylin.dimension.DictionaryDimEnc$DictionarySerializer.serialize(DictionaryDimEnc.java:121) > at > org.apache.kylin.cube.gridtable.CubeCodeSystem.encodeColumnValue(CubeCodeSystem.java:121) > at > org.apache.kylin.cube.gridtable.CubeCodeSystem.encodeColumnValue(CubeCodeSystem.java:110) > at org.apache.kylin.gridtable.GTRecord.setValues(GTRecord.java:93) > at org.apache.kylin.gridtable.GTRecord.setValues(GTRecord.java:81) > at > org.apache.kylin.cube.inmemcubing.InMemCubeBuilderInputConverter.convert(InMemCubeBuilderInputConverter.java:74) > at > org.apache.kylin.cube.inmemcubing.InMemCubeBuilder$InputConverter$1.next(InMemCubeBuilder.java:544) > at > org.apache.kylin.cube.inmemcubing.InMemCubeBuilder$InputConverter$1.next(InMemCubeBuilder.java:525) > at > org.apache.kylin.gridtable.GTAggregateScanner.iterator(GTAggregateScanner.java:139) > at > org.apache.kylin.cube.inmemcubing.InMemCubeBuilder.createBaseCuboid(InMemCubeBuilder.java:341) > at > org.apache.kylin.cube.inmemcubing.InMemCubeBuilder.build(InMemCubeBuilder.java:168) > at > org.apache.kylin.cube.inmemcubing.InMemCubeBuilder.build(InMemCubeBuilder.java:137) > at > org.apache.kylin.cube.inmemcubing.DoggedCubeBuilder$SplitThread.run(DoggedCubeBuilder.java:284) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
