[jira] [Updated] (KYLIN-1106) Can not send email caused by Build Base Cuboid Data step failed
[ https://issues.apache.org/jira/browse/KYLIN-1106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaofeng SHI updated KYLIN-1106: Assignee: liyang Fix Version/s: v1.2 v2.0 > Can not send email caused by Build Base Cuboid Data step failed > --- > > Key: KYLIN-1106 > URL: https://issues.apache.org/jira/browse/KYLIN-1106 > Project: Kylin > Issue Type: Bug >Affects Versions: v1.1, v1.0 >Reporter: fengYu >Assignee: liyang > Fix For: v2.0, v1.2 > > > I build a cube but it failed in the "Build Base Cuboid Data" step, I can not > get job failed email and find the stacktrace in log : > java.lang.NullPointerException > at java.util.regex.Matcher.appendReplacement(Matcher.java:758) > at java.util.regex.Matcher.replaceAll(Matcher.java:906) > at java.lang.String.replaceAll(String.java:2162) > at > org.apache.kylin.job.cube.CubingJob.formatNotifications(CubingJob.java:98) > at > org.apache.kylin.job.execution.AbstractExecutable.notifyUserStatusChange(AbstractExecutable.java:211) > at > org.apache.kylin.job.execution.DefaultChainedExecutable.onExecuteFinished(DefaultChainedExecutable.java:101) > at > org.apache.kylin.job.cube.CubingJob.onExecuteFinished(CubingJob.java:130) > at > org.apache.kylin.job.execution.AbstractExecutable.execute(AbstractExecutable.java:113) > at > org.apache.kylin.job.impl.threadpool.DefaultScheduler$JobRunner.run(DefaultScheduler.java:130) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:745) > This is caused by CubingJob.getSourceRecordCount() function return null while > get this job input source recode, So here need a recheck before return . -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KYLIN-1195) Conflict of Jersey-core.jar caused ClassCastException when building a cube
[ https://issues.apache.org/jira/browse/KYLIN-1195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15037167#comment-15037167 ] Shaofeng SHI commented on KYLIN-1195: - I created a new binary package from my MAC, in the kylin.war, there is no jersey libs, so I couldn't reproduce it now. Later I will request a clean ubuntu machine to take a try. > Conflict of Jersey-core.jar caused ClassCastException when building a cube > -- > > Key: KYLIN-1195 > URL: https://issues.apache.org/jira/browse/KYLIN-1195 > Project: Kylin > Issue Type: Bug > Components: Job Engine >Affects Versions: v2.0 > Environment: Os: Ubuntu 12.04.4 LTS > Java: java version "1.7.0_67" > Java(TM) SE Runtime Environment (build 1.7.0_67-b01) > Java HotSpot(TM) 64-Bit Server VM (build 24.65-b04, mixed mode) > HDP: 2.2.9.0-3393 >Reporter: Vic Wang >Assignee: ZhouQianhao > > java.lang.LinkageError: ClassCastException: attempting to > castjar:file:/usr/local/kylin/tomcat/webapps/kylin/WEB-INF/lib/jersey-core-1.9.jar!/javax/ws/rs/ext/RuntimeDelegate.classtojar:file:/usr/hdp/2.2.9.0-3393/hbase/lib/jersey-core-1.8.jar!/javax/ws/rs/ext/RuntimeDelegate.class > at > javax.ws.rs.ext.RuntimeDelegate.findDelegate(RuntimeDelegate.java:116) > at javax.ws.rs.ext.RuntimeDelegate.getInstance(RuntimeDelegate.java:91) > at javax.ws.rs.core.MediaType.(MediaType.java:44) > at com.sun.jersey.core.header.MediaTypes.(MediaTypes.java:64) > at > com.sun.jersey.core.spi.factory.MessageBodyFactory.initReaders(MessageBodyFactory.java:182) > at > com.sun.jersey.core.spi.factory.MessageBodyFactory.initReaders(MessageBodyFactory.java:175) > at > com.sun.jersey.core.spi.factory.MessageBodyFactory.init(MessageBodyFactory.java:162) > at com.sun.jersey.api.client.Client.init(Client.java:342) > at com.sun.jersey.api.client.Client.access$000(Client.java:118) > at com.sun.jersey.api.client.Client$1.f(Client.java:191) > at com.sun.jersey.api.client.Client$1.f(Client.java:187) > at com.sun.jersey.spi.inject.Errors.processWithErrors(Errors.java:193) > at com.sun.jersey.api.client.Client.(Client.java:187) > at com.sun.jersey.api.client.Client.(Client.java:170) > at > org.apache.hadoop.yarn.client.api.impl.TimelineClientImpl.serviceInit(TimelineClientImpl.java:340) > at > org.apache.hadoop.service.AbstractService.init(AbstractService.java:163) > at > org.apache.hadoop.yarn.client.api.impl.YarnClientImpl.serviceInit(YarnClientImpl.java:164) > at > org.apache.hadoop.service.AbstractService.init(AbstractService.java:163) > at > org.apache.hadoop.mapred.ResourceMgrDelegate.serviceInit(ResourceMgrDelegate.java:102) > at > org.apache.hadoop.service.AbstractService.init(AbstractService.java:163) > at > org.apache.hadoop.mapred.ResourceMgrDelegate.(ResourceMgrDelegate.java:96) > at org.apache.hadoop.mapred.YARNRunner.(YARNRunner.java:112) > at > org.apache.hadoop.mapred.YarnClientProtocolProvider.create(YarnClientProtocolProvider.java:34) > at org.apache.hadoop.mapreduce.Cluster.initialize(Cluster.java:95) > at org.apache.hadoop.mapreduce.Cluster.(Cluster.java:82) > at org.apache.hadoop.mapreduce.Cluster.(Cluster.java:75) > at org.apache.hadoop.mapreduce.Job$9.run(Job.java:1267) > at org.apache.hadoop.mapreduce.Job$9.run(Job.java:1263) > at java.security.AccessController.doPrivileged(Native Method) > at javax.security.auth.Subject.doAs(Subject.java:415) > at > org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1671) > at org.apache.hadoop.mapreduce.Job.connect(Job.java:1262) > at org.apache.hadoop.mapreduce.Job.submit(Job.java:1291) > at > org.apache.kylin.engine.mr.common.AbstractHadoopJob.waitForCompletion(AbstractHadoopJob.java:129) > at > org.apache.kylin.engine.mr.steps.FactDistinctColumnsJob.run(FactDistinctColumnsJob.java:92) > at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:76) > at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:90) > at > org.apache.kylin.engine.mr.common.MapReduceExecutable.doWork(MapReduceExecutable.java:119) > at > org.apache.kylin.job.execution.AbstractExecutable.execute(AbstractExecutable.java:107) > at > org.apache.kylin.job.execution.DefaultChainedExecutable.doWork(DefaultChainedExecutable.java:50) > at > org.apache.kylin.job.execution.AbstractExecutable.execute(AbstractExecutable.java:107) > at > org.apache.kylin.job.impl.threadpool.DefaultScheduler$JobRunner.run(DefaultScheduler.java:124) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at > jav
[jira] [Assigned] (KYLIN-1195) Conflict of Jersey-core.jar caused ClassCastException when building a cube
[ https://issues.apache.org/jira/browse/KYLIN-1195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaofeng SHI reassigned KYLIN-1195: --- Assignee: Shaofeng SHI (was: ZhouQianhao) > Conflict of Jersey-core.jar caused ClassCastException when building a cube > -- > > Key: KYLIN-1195 > URL: https://issues.apache.org/jira/browse/KYLIN-1195 > Project: Kylin > Issue Type: Bug > Components: Job Engine >Affects Versions: v2.0 > Environment: Os: Ubuntu 12.04.4 LTS > Java: java version "1.7.0_67" > Java(TM) SE Runtime Environment (build 1.7.0_67-b01) > Java HotSpot(TM) 64-Bit Server VM (build 24.65-b04, mixed mode) > HDP: 2.2.9.0-3393 >Reporter: Vic Wang >Assignee: Shaofeng SHI > > java.lang.LinkageError: ClassCastException: attempting to > castjar:file:/usr/local/kylin/tomcat/webapps/kylin/WEB-INF/lib/jersey-core-1.9.jar!/javax/ws/rs/ext/RuntimeDelegate.classtojar:file:/usr/hdp/2.2.9.0-3393/hbase/lib/jersey-core-1.8.jar!/javax/ws/rs/ext/RuntimeDelegate.class > at > javax.ws.rs.ext.RuntimeDelegate.findDelegate(RuntimeDelegate.java:116) > at javax.ws.rs.ext.RuntimeDelegate.getInstance(RuntimeDelegate.java:91) > at javax.ws.rs.core.MediaType.(MediaType.java:44) > at com.sun.jersey.core.header.MediaTypes.(MediaTypes.java:64) > at > com.sun.jersey.core.spi.factory.MessageBodyFactory.initReaders(MessageBodyFactory.java:182) > at > com.sun.jersey.core.spi.factory.MessageBodyFactory.initReaders(MessageBodyFactory.java:175) > at > com.sun.jersey.core.spi.factory.MessageBodyFactory.init(MessageBodyFactory.java:162) > at com.sun.jersey.api.client.Client.init(Client.java:342) > at com.sun.jersey.api.client.Client.access$000(Client.java:118) > at com.sun.jersey.api.client.Client$1.f(Client.java:191) > at com.sun.jersey.api.client.Client$1.f(Client.java:187) > at com.sun.jersey.spi.inject.Errors.processWithErrors(Errors.java:193) > at com.sun.jersey.api.client.Client.(Client.java:187) > at com.sun.jersey.api.client.Client.(Client.java:170) > at > org.apache.hadoop.yarn.client.api.impl.TimelineClientImpl.serviceInit(TimelineClientImpl.java:340) > at > org.apache.hadoop.service.AbstractService.init(AbstractService.java:163) > at > org.apache.hadoop.yarn.client.api.impl.YarnClientImpl.serviceInit(YarnClientImpl.java:164) > at > org.apache.hadoop.service.AbstractService.init(AbstractService.java:163) > at > org.apache.hadoop.mapred.ResourceMgrDelegate.serviceInit(ResourceMgrDelegate.java:102) > at > org.apache.hadoop.service.AbstractService.init(AbstractService.java:163) > at > org.apache.hadoop.mapred.ResourceMgrDelegate.(ResourceMgrDelegate.java:96) > at org.apache.hadoop.mapred.YARNRunner.(YARNRunner.java:112) > at > org.apache.hadoop.mapred.YarnClientProtocolProvider.create(YarnClientProtocolProvider.java:34) > at org.apache.hadoop.mapreduce.Cluster.initialize(Cluster.java:95) > at org.apache.hadoop.mapreduce.Cluster.(Cluster.java:82) > at org.apache.hadoop.mapreduce.Cluster.(Cluster.java:75) > at org.apache.hadoop.mapreduce.Job$9.run(Job.java:1267) > at org.apache.hadoop.mapreduce.Job$9.run(Job.java:1263) > at java.security.AccessController.doPrivileged(Native Method) > at javax.security.auth.Subject.doAs(Subject.java:415) > at > org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1671) > at org.apache.hadoop.mapreduce.Job.connect(Job.java:1262) > at org.apache.hadoop.mapreduce.Job.submit(Job.java:1291) > at > org.apache.kylin.engine.mr.common.AbstractHadoopJob.waitForCompletion(AbstractHadoopJob.java:129) > at > org.apache.kylin.engine.mr.steps.FactDistinctColumnsJob.run(FactDistinctColumnsJob.java:92) > at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:76) > at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:90) > at > org.apache.kylin.engine.mr.common.MapReduceExecutable.doWork(MapReduceExecutable.java:119) > at > org.apache.kylin.job.execution.AbstractExecutable.execute(AbstractExecutable.java:107) > at > org.apache.kylin.job.execution.DefaultChainedExecutable.doWork(DefaultChainedExecutable.java:50) > at > org.apache.kylin.job.execution.AbstractExecutable.execute(AbstractExecutable.java:107) > at > org.apache.kylin.job.impl.threadpool.DefaultScheduler$JobRunner.run(DefaultScheduler.java:124) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:745) -- This message was sent by Atlassian JIRA (v6.3.4#6332
[jira] [Resolved] (KYLIN-1195) Conflict of Jersey-core.jar caused ClassCastException when building a cube
[ https://issues.apache.org/jira/browse/KYLIN-1195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaofeng SHI resolved KYLIN-1195. - Resolution: Not A Problem This is concluded as a maven version issue; Vic was using ubuntu's default maven, which is v3.0; After upgrade to a newer version, the binary package doesn't have those jars; On my mac, the maven version is 3.2.3. > Conflict of Jersey-core.jar caused ClassCastException when building a cube > -- > > Key: KYLIN-1195 > URL: https://issues.apache.org/jira/browse/KYLIN-1195 > Project: Kylin > Issue Type: Bug > Components: Job Engine >Affects Versions: v2.0 > Environment: Os: Ubuntu 12.04.4 LTS > Java: java version "1.7.0_67" > Java(TM) SE Runtime Environment (build 1.7.0_67-b01) > Java HotSpot(TM) 64-Bit Server VM (build 24.65-b04, mixed mode) > HDP: 2.2.9.0-3393 >Reporter: Vic Wang >Assignee: Shaofeng SHI > > java.lang.LinkageError: ClassCastException: attempting to > castjar:file:/usr/local/kylin/tomcat/webapps/kylin/WEB-INF/lib/jersey-core-1.9.jar!/javax/ws/rs/ext/RuntimeDelegate.classtojar:file:/usr/hdp/2.2.9.0-3393/hbase/lib/jersey-core-1.8.jar!/javax/ws/rs/ext/RuntimeDelegate.class > at > javax.ws.rs.ext.RuntimeDelegate.findDelegate(RuntimeDelegate.java:116) > at javax.ws.rs.ext.RuntimeDelegate.getInstance(RuntimeDelegate.java:91) > at javax.ws.rs.core.MediaType.(MediaType.java:44) > at com.sun.jersey.core.header.MediaTypes.(MediaTypes.java:64) > at > com.sun.jersey.core.spi.factory.MessageBodyFactory.initReaders(MessageBodyFactory.java:182) > at > com.sun.jersey.core.spi.factory.MessageBodyFactory.initReaders(MessageBodyFactory.java:175) > at > com.sun.jersey.core.spi.factory.MessageBodyFactory.init(MessageBodyFactory.java:162) > at com.sun.jersey.api.client.Client.init(Client.java:342) > at com.sun.jersey.api.client.Client.access$000(Client.java:118) > at com.sun.jersey.api.client.Client$1.f(Client.java:191) > at com.sun.jersey.api.client.Client$1.f(Client.java:187) > at com.sun.jersey.spi.inject.Errors.processWithErrors(Errors.java:193) > at com.sun.jersey.api.client.Client.(Client.java:187) > at com.sun.jersey.api.client.Client.(Client.java:170) > at > org.apache.hadoop.yarn.client.api.impl.TimelineClientImpl.serviceInit(TimelineClientImpl.java:340) > at > org.apache.hadoop.service.AbstractService.init(AbstractService.java:163) > at > org.apache.hadoop.yarn.client.api.impl.YarnClientImpl.serviceInit(YarnClientImpl.java:164) > at > org.apache.hadoop.service.AbstractService.init(AbstractService.java:163) > at > org.apache.hadoop.mapred.ResourceMgrDelegate.serviceInit(ResourceMgrDelegate.java:102) > at > org.apache.hadoop.service.AbstractService.init(AbstractService.java:163) > at > org.apache.hadoop.mapred.ResourceMgrDelegate.(ResourceMgrDelegate.java:96) > at org.apache.hadoop.mapred.YARNRunner.(YARNRunner.java:112) > at > org.apache.hadoop.mapred.YarnClientProtocolProvider.create(YarnClientProtocolProvider.java:34) > at org.apache.hadoop.mapreduce.Cluster.initialize(Cluster.java:95) > at org.apache.hadoop.mapreduce.Cluster.(Cluster.java:82) > at org.apache.hadoop.mapreduce.Cluster.(Cluster.java:75) > at org.apache.hadoop.mapreduce.Job$9.run(Job.java:1267) > at org.apache.hadoop.mapreduce.Job$9.run(Job.java:1263) > at java.security.AccessController.doPrivileged(Native Method) > at javax.security.auth.Subject.doAs(Subject.java:415) > at > org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1671) > at org.apache.hadoop.mapreduce.Job.connect(Job.java:1262) > at org.apache.hadoop.mapreduce.Job.submit(Job.java:1291) > at > org.apache.kylin.engine.mr.common.AbstractHadoopJob.waitForCompletion(AbstractHadoopJob.java:129) > at > org.apache.kylin.engine.mr.steps.FactDistinctColumnsJob.run(FactDistinctColumnsJob.java:92) > at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:76) > at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:90) > at > org.apache.kylin.engine.mr.common.MapReduceExecutable.doWork(MapReduceExecutable.java:119) > at > org.apache.kylin.job.execution.AbstractExecutable.execute(AbstractExecutable.java:107) > at > org.apache.kylin.job.execution.DefaultChainedExecutable.doWork(DefaultChainedExecutable.java:50) > at > org.apache.kylin.job.execution.AbstractExecutable.execute(AbstractExecutable.java:107) > at > org.apache.kylin.job.impl.threadpool.DefaultScheduler$JobRunner.run(DefaultScheduler.java:124) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) >
[jira] [Updated] (KYLIN-1189) Automatically resume running jobs when job engine failover
[ https://issues.apache.org/jira/browse/KYLIN-1189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaofeng SHI updated KYLIN-1189: Fix Version/s: v2.1 > Automatically resume running jobs when job engine failover > -- > > Key: KYLIN-1189 > URL: https://issues.apache.org/jira/browse/KYLIN-1189 > Project: Kylin > Issue Type: Sub-task > Components: Job Engine >Reporter: Shaofeng SHI >Assignee: Shaofeng SHI > Fix For: v2.1 > > > When Kylin's job engine failover, it will put all running job to "ERROR". > User need manually resume such jobs to move ahead. This should be automated > when we implement the auto-balance and HA. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KYLIN-1188) Kylin node self-discover
[ https://issues.apache.org/jira/browse/KYLIN-1188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaofeng SHI updated KYLIN-1188: Fix Version/s: v2.1 > Kylin node self-discover > > > Key: KYLIN-1188 > URL: https://issues.apache.org/jira/browse/KYLIN-1188 > Project: Kylin > Issue Type: Sub-task > Components: General >Reporter: Shaofeng SHI >Assignee: Shaofeng SHI > Fix For: v2.1 > > > This is a sub task for Kylin's cluster management. > When a new Kylin node is started, it need be added into the cluster > automatically, and then start to work with existing nodes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KYLIN-1117) cluster management
[ https://issues.apache.org/jira/browse/KYLIN-1117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaofeng SHI updated KYLIN-1117: Fix Version/s: v2.1 > cluster management > -- > > Key: KYLIN-1117 > URL: https://issues.apache.org/jira/browse/KYLIN-1117 > Project: Kylin > Issue Type: Task > Components: General >Reporter: ZhouQianhao >Assignee: Shaofeng SHI > Fix For: v2.1 > > Original Estimate: 1,344h > Remaining Estimate: 1,344h > > Kylin currently manages the cluster itself, so far it works fine since there > are only 2 roles for the cluster, job engine and query engine. > However when new features such as streaming is coming, deployment will be > more complex. > So new cluster management should be introduced. All the tasks followed or > related can be created as a sub-task -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KYLIN-1148) Edit project's name and cancel edit, project's name still modified
[ https://issues.apache.org/jira/browse/KYLIN-1148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaofeng SHI updated KYLIN-1148: Fix Version/s: v1.2 > Edit project's name and cancel edit, project's name still modified > -- > > Key: KYLIN-1148 > URL: https://issues.apache.org/jira/browse/KYLIN-1148 > Project: Kylin > Issue Type: Bug > Components: Web >Affects Versions: v1.1.1 >Reporter: nichunen >Assignee: Zhong,Jason > Fix For: v1.2 > > Attachments: KYLIN-1148.patch > > > At the projects page, suppose a project with name "name1". Edit its name to > "name2", then cancel edit. On the UI, the project's name can not be rolled > back. > Attached is a patch to fix this issue. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KYLIN-1148) Edit project's name and cancel edit, project's name still modified
[ https://issues.apache.org/jira/browse/KYLIN-1148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15037584#comment-15037584 ] Shaofeng SHI commented on KYLIN-1148: - [~zhongjian] Jason, can you review this patch and merge it in v1.2 release? thanks! > Edit project's name and cancel edit, project's name still modified > -- > > Key: KYLIN-1148 > URL: https://issues.apache.org/jira/browse/KYLIN-1148 > Project: Kylin > Issue Type: Bug > Components: Web >Affects Versions: v1.1.1 >Reporter: nichunen >Assignee: Zhong,Jason > Fix For: v1.2 > > Attachments: KYLIN-1148.patch > > > At the projects page, suppose a project with name "name1". Edit its name to > "name2", then cancel edit. On the UI, the project's name can not be rolled > back. > Attached is a patch to fix this issue. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KYLIN-1108) Return Type Empty When Measure-> Count In Cube Design
[ https://issues.apache.org/jira/browse/KYLIN-1108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaofeng SHI updated KYLIN-1108: Fix Version/s: (was: 2.0) (was: 1.2) v1.2 v2.0 > Return Type Empty When Measure-> Count In Cube Design > - > > Key: KYLIN-1108 > URL: https://issues.apache.org/jira/browse/KYLIN-1108 > Project: Kylin > Issue Type: Bug > Components: Web >Affects Versions: Future > Environment: CentOS6.5+HDP2.3 >Reporter: Yiming Liu >Assignee: Zhong,Jason >Priority: Minor > Fix For: v2.0, v1.2 > > > In Cube Designer, Measure Panel. > Add Measure, select "COUNT" expression, the return type is "empty". > But if select "SUM" first, then select "COUNT", the return type will be > "BIGINT". -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KYLIN-1149) When yarn return an incomplete job tracking URL, Kylin will fail to get job status
[
https://issues.apache.org/jira/browse/KYLIN-1149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shaofeng SHI updated KYLIN-1149:
Fix Version/s: (was: 1.2)
v1.2
> When yarn return an incomplete job tracking URL, Kylin will fail to get job
> status
> --
>
> Key: KYLIN-1149
> URL: https://issues.apache.org/jira/browse/KYLIN-1149
> Project: Kylin
> Issue Type: Bug
> Components: Job Engine
>Affects Versions: v1.1, v1.0, v0.7.2, v0.7.1, v1.1.1
>Reporter: Shaofeng SHI
>Assignee: Shaofeng SHI
> Fix For: v2.0, v1.2
>
>
> When yarn return an incomplete job tracking URL, Kylin will fail to get job
> status, then the cube job will be in "Error" state:
> {code}
> [pool-9-thread-8]:[2015-11-16
> 04:58:32,062][ERROR][org.apache.kylin.engine.mr.common.HadoopStatusChecker.checkStatus(HadoopStatusChecker.java:91)]
> - error check status
> java.lang.IllegalArgumentException: host parameter is null
> at
> org.apache.commons.httpclient.HttpConnection.setHost(HttpConnection.java:249)
> at
> org.apache.commons.httpclient.SimpleHttpConnectionManager.getConnectionWithTimeout(SimpleHttpConnectionManager.java:189)
> at
> org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:153)
> at
> org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:397)
> at
> org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:323)
> at
> org.apache.kylin.engine.mr.common.HadoopStatusGetter.getHttpResponse(HadoopStatusGetter.java:77)
> at
> org.apache.kylin.engine.mr.common.HadoopStatusGetter.get(HadoopStatusGetter.java:54)
> at
> org.apache.kylin.engine.mr.common.HadoopStatusChecker.checkStatus(HadoopStatusChecker.java:56)
> at
> org.apache.kylin.engine.mr.common.MapReduceExecutable.doWork(MapReduceExecutable.java:136)
> at
> org.apache.kylin.job.execution.AbstractExecutable.execute(AbstractExecutable.java:107)
> at
> org.apache.kylin.job.execution.DefaultChainedExecutable.doWork(DefaultChainedExecutable.java:50)
> at
> org.apache.kylin.job.execution.AbstractExecutable.execute(AbstractExecutable.java:107)
> at
> org.apache.kylin.job.impl.threadpool.DefaultScheduler$JobRunner.run(DefaultScheduler.java:124)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> Kylin should better check whether the URL is valid before visit it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KYLIN-1186) Support precise Count Distinct using bitmap
[ https://issues.apache.org/jira/browse/KYLIN-1186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaofeng SHI updated KYLIN-1186: Fix Version/s: (was: 1.2) v1.3 Yang is doing a refactoring on MeasureDesc, idealy after this refactor, it will be much easier to implement custom measure than now. I put this to v1.3 as we're going to release v1.2 soon. > Support precise Count Distinct using bitmap > --- > > Key: KYLIN-1186 > URL: https://issues.apache.org/jira/browse/KYLIN-1186 > Project: Kylin > Issue Type: Improvement > Components: Job Engine >Affects Versions: v1.1 >Reporter: Yerui Sun >Assignee: ZhouQianhao > Fix For: v2.0, v1.3 > > Original Estimate: 168h > Remaining Estimate: 168h > > For now, kylin only support non-precise count distinct by hyperloglog. > In our production scenario, there're strongly requirements for precise count > distinct, mainly for the column of type int or bigint, such as user-id, > product-id, etc. > Implementing of precise count distinct for all types is difficult and not > efficiency. However, only supporting int or bigint make this much easier. The > values can be projected into a bitmap, which is easy to be compressed and > stored, and easy to count. > I've created a POC based on RoaringBitmap, proving that worked. There's some > more work to be done: > * RoaringBitmap only support int, there need a solution to support bigint; > * Add a new measure and codec, like HyperLogLogPlusCounter, make it easy to > use; > * Add new measure on web ui, and check that whether the column type is int > or bigint; -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KYLIN-1105) Cache in AbstractRowKeyEncoder.createInstance() is useless
[ https://issues.apache.org/jira/browse/KYLIN-1105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaofeng SHI updated KYLIN-1105: Fix Version/s: (was: 2.0) (was: 1.2) v1.2 v2.0 > Cache in AbstractRowKeyEncoder.createInstance() is useless > -- > > Key: KYLIN-1105 > URL: https://issues.apache.org/jira/browse/KYLIN-1105 > Project: Kylin > Issue Type: Bug >Reporter: liyang >Assignee: liyang > Fix For: v2.0, v1.2 > > > The current cache in AbstractRowKeyEncoder.createInstance() is not > implemented correctly. Put key being cube name and get key being segment > table name, the cache will never hit. > Also don't see a strong reason why the row key encoder needs a cache. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KYLIN-1058) Remove "right join" during model creation
[ https://issues.apache.org/jira/browse/KYLIN-1058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaofeng SHI updated KYLIN-1058: Fix Version/s: (was: 2.0) (was: 1.2) v1.2 v2.0 > Remove "right join" during model creation > - > > Key: KYLIN-1058 > URL: https://issues.apache.org/jira/browse/KYLIN-1058 > Project: Kylin > Issue Type: Bug >Reporter: liyang >Assignee: Zhong,Jason > Fix For: v2.0, v1.2 > > > I don't think Kylin support "right join" (in addition to inner join and left > join). Remove it in model creation options. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KYLIN-1070) changing case in table name in model desc
[ https://issues.apache.org/jira/browse/KYLIN-1070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaofeng SHI updated KYLIN-1070: Fix Version/s: (was: 1.2) v1.2 > changing case in table name in model desc > --- > > Key: KYLIN-1070 > URL: https://issues.apache.org/jira/browse/KYLIN-1070 > Project: Kylin > Issue Type: Bug > Components: Job Engine >Affects Versions: v1.1, 1.x-HBase1.1.3 >Reporter: vipin >Assignee: Shaofeng SHI >Priority: Minor > Fix For: v1.2 > > Attachments: kylin_1070.patch > > > with v1.1-release version lets say if i am sending cube request having table > name in camel case > ,its get persisted and in package org.apache.kylin.job.JoinedFlatTable > map returned by private static Map > buildTableAliasMap(DataModelDesc dataModelDesc) method > has camel case table name as send from request, while IntermediateColumnDesc > has upper case table names > table name which we get from intermediateTableDesc.getDataModel() is same as > request while > intermediateTableDesc.getColumnList() has upper case table name > I have checked in hbase : > get 'kylin_metadata' ,'/model_desc/TestSimple_114.json' -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KYLIN-1030) Backport Data Model Editor to 1.x branch
[ https://issues.apache.org/jira/browse/KYLIN-1030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaofeng SHI updated KYLIN-1030: Fix Version/s: (was: v1.2) v1.3 Move to further release. > Backport Data Model Editor to 1.x branch > > > Key: KYLIN-1030 > URL: https://issues.apache.org/jira/browse/KYLIN-1030 > Project: Kylin > Issue Type: Improvement > Components: Web >Affects Versions: v1.0 >Reporter: Luke Han >Assignee: Zhong,Jason > Fix For: v1.3 > > > Currently, 1.x branch do not support edit data model directly which blocked > some cases to refine data model even raise exceptions. > Back port Data Model Editor from 2.x branch to support edit data mode from UI > by cube admin/editor. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KYLIN-558) Quota management support by project
[ https://issues.apache.org/jira/browse/KYLIN-558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaofeng SHI updated KYLIN-558: --- Fix Version/s: (was: v1.2) Backlog > Quota management support by project > --- > > Key: KYLIN-558 > URL: https://issues.apache.org/jira/browse/KYLIN-558 > Project: Kylin > Issue Type: Wish > Components: General >Reporter: Luke Han >Assignee: Luke Han > Fix For: Backlog > > > Cube technology is using space swap time: pre-calculate result and store to > somewhere for further query, since the result already there, there's no > runtime scan in query phase. > Although Kylin have good design to optimize final cube size, but in reality, > storage and computing resources always have limitation. To well balance > between each project, this feature will enable quota by project: > 1. Entire system will have one setting for total quota, could set by admin or > read from HBase/Hive > 2. Each project will have quota setting, default value will be set in > kylin.propertiies file > 3. Admin can update that value of each project. > 4. Every cube build job should inquire it's project quota and compare to used > storage, denied process to next step if the used storage already exceed quota > 5. System should alert project owner and admin when used storage close to 85% > of quota or exceeded > Same policy also should extend to MR job, Hive and others. > Target Release: v0.7.3 - capacity and automation -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KYLIN-518) Cannot select Right join type if current join type is Left join type
[ https://issues.apache.org/jira/browse/KYLIN-518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaofeng SHI updated KYLIN-518: --- Assignee: Zhong,Jason Fix Version/s: (was: v1.2) Backlog > Cannot select Right join type if current join type is Left join type > > > Key: KYLIN-518 > URL: https://issues.apache.org/jira/browse/KYLIN-518 > Project: Kylin > Issue Type: Wish > Components: Web >Reporter: janefeng >Assignee: Zhong,Jason > Fix For: Backlog > > Attachments: screenshot-1.png > > > 1. Open Add Lookup window > 2. Select a Lookup Table name, such as Test_CATEGORY_GROUPINGS. > 3. Select Left join type. > 4. Select Right join type. > Actual Result: > Cannot select Right join type. > Expected Result: > Can switch to any one join type. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KYLIN-393) ssh port should not fixed
[ https://issues.apache.org/jira/browse/KYLIN-393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaofeng SHI updated KYLIN-393: --- Fix Version/s: (was: v1.2) Backlog > ssh port should not fixed > - > > Key: KYLIN-393 > URL: https://issues.apache.org/jira/browse/KYLIN-393 > Project: Kylin > Issue Type: Wish > Components: Job Engine >Affects Versions: v0.7.1 >Reporter: Luke Han >Assignee: hongbin ma > Labels: github-import, newbie > Fix For: Backlog > > > Kylin / common / src / main / java / com / kylinolap / common / util / > SSHClient.java > ssh port should not fixed > jsch.getSession(username, hostname, 22); > Imported from GitHub > Url: https://github.com/KylinOLAP/Kylin/issues/112 > Created by: [fly3q|https://github.com/fly3q] > Labels: enhancement, > Assignee: [binmahone|https://github.com/binmahone] > Created at: Wed Nov 26 13:01:47 CST 2014 > State: open -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KYLIN-242) Kylin Cuboid Whitelist
[ https://issues.apache.org/jira/browse/KYLIN-242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaofeng SHI updated KYLIN-242: --- Assignee: hongbin ma (was: liyang) Fix Version/s: (was: v1.2) v2.1 > Kylin Cuboid Whitelist > -- > > Key: KYLIN-242 > URL: https://issues.apache.org/jira/browse/KYLIN-242 > Project: Kylin > Issue Type: Improvement > Components: General >Reporter: Luke Han >Assignee: hongbin ma > Labels: github-import > Fix For: v2.1 > > > Proposal from Hongbin about Cuboid White List: > * More detail, please refer to Kylin Dev mailing list: > d...@kylin.incubator.apache.org > Logically, a cube contains cuboids representing all combinations of > dimensions. Apparently, a naive cube building strategy that materializes > all cuboids will easily meet curse-of-dimension problems. Currently Kylin > leverages a strategy called "aggregation groups" to reduce the number of > cuboids need being materialized. > However, if the query pattern is simple and fixed, the "aggregation group" > strategy is still not efficient enough. For example, suppose there're five > dimensions, namely A,B,C,D and E. The data modeler is sure that only > combinations (A,B,C), (D,E), (A,E) will be queried, so he’ll use the > aggregation group tool to optimize his cube definition. However, whatever > aggregation group he chooses, lots of useless combinations would be > materialized. > With a new strategy called "cuboid whitelist", data modelers can guide > Kylin to only materialize the cuboids he's interested in. Depending on the > whitelist, Kylin will materialize the minimal set of cuboids to cover each > cuboid in the whitelist. To support this, the following functionalities > should be added: > 1. Front-end/UI for specifying whitelist members, and persistent them to > cube description. > 2. Enhanced job engine scheduler that will calculate a minimal spanning > build tree based on the whitelist. > 3. (OPTIONAL) Enhanced job engine to support dynamic whitelist, trigger new > builds for lately added whitelist members. > Hongbin Ma > Imported from GitHub > Url: https://github.com/KylinOLAP/Kylin/issues/263 > Created by: [lukehan|https://github.com/lukehan] > Labels: enhancement, > Milestone: Backlog > Assignee: [binmahone|https://github.com/binmahone] > Created at: Thu Dec 25 13:17:11 CST 2014 > State: open -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KYLIN-218) Job Engine Runtime monitoring page
[ https://issues.apache.org/jira/browse/KYLIN-218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaofeng SHI updated KYLIN-218: --- Fix Version/s: (was: v1.2) Backlog > Job Engine Runtime monitoring page > -- > > Key: KYLIN-218 > URL: https://issues.apache.org/jira/browse/KYLIN-218 > Project: Kylin > Issue Type: Wish > Components: Web >Reporter: Luke Han >Assignee: Zhong,Jason > Labels: github-import > Fix For: Backlog > > > As administrator, I would like to have one admin page to monitoring Job > Engine's runtime performance, queue, jobs, exceptions and so on. > Imported from GitHub > Url: https://github.com/KylinOLAP/Kylin/issues/287 > Created by: [lukehan|https://github.com/lukehan] > Labels: newfeature, > Milestone: Backlog > Created at: Fri Dec 26 14:22:51 CST 2014 > State: open -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KYLIN-201) Save as image in visualization result
[ https://issues.apache.org/jira/browse/KYLIN-201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaofeng SHI updated KYLIN-201: --- Fix Version/s: (was: v1.2) Backlog > Save as image in visualization result > - > > Key: KYLIN-201 > URL: https://issues.apache.org/jira/browse/KYLIN-201 > Project: Kylin > Issue Type: Wish >Reporter: Luke Han >Assignee: Zhong,Jason > Labels: github-import > Fix For: Backlog > > > As a user, I would like to be able to save visualization as image > The "Export" should perform different approach for Grid and Visualization > view. > ![image|https://cloud.githubusercontent.com/assets/1104017/5556235/af5ddb12-8d0f-11e4-91f9-34bafe13c163.png] > Imported from GitHub > Url: https://github.com/KylinOLAP/Kylin/issues/304 > Created by: [lukehan|https://github.com/lukehan] > Labels: enhancement, > Created at: Fri Dec 26 14:58:59 CST 2014 > State: open -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KYLIN-1172) kylin support multi-hive on different hadoop cluster
[ https://issues.apache.org/jira/browse/KYLIN-1172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaofeng SHI updated KYLIN-1172: Fix Version/s: v1.3 > kylin support multi-hive on different hadoop cluster > > > Key: KYLIN-1172 > URL: https://issues.apache.org/jira/browse/KYLIN-1172 > Project: Kylin > Issue Type: Improvement >Affects Versions: v1.0 >Reporter: fengYu > Fix For: v1.3 > > Attachments: > 0001-support-more-hives-depend-on-different-hadoop-add-co.patch, > 0001-support-more-hives-depend-on-different-hadoop.patch > > > Hi, I recently modify kylin to support multi-hive on different hadoop > cluster and take them as input source to kylin, we do this since the > following reasons: > 1、we have more than one hadoop cluster and many hive depend on them(products > may has its own hive), we cannot migrate those hives to one and don't want to > deploy one kylin for every hive source. > 2、our hadoop cluster deploy in different DC, we need to support them in one > kylin instance. > 3、source data in hive is much less than hfile, so copy those files cross > different different is more efficient(fact distinct column job and base > cuboid job need take datas at hive as input), so we deploy hbase and hadoop > in one DC (separated in different HDFS). > So, we divide data flow into 3 parts, hive is input source, hadoop do > computing which will generate many temporary files, hbase is output. After > cube building, queries on kylin just interactive with hbase. therefore, what > we need to do is how to build cube base on differnet hives and hadoops. > Our method are summarized below : > 1、Deploy hive and hadoops, before start kylin, user should deploy all hives > and hadoop, and ensure you can run hive sql in ./hive. and access every HDFS > with 'hadoop fs 'command(add more nameservice in hdfs-site.xml). > 2、Divide hives into two part: the hive that used when kylin start(we call it > default one) and others are additional, we should allocate a name for every > hive (default one is null), For simplicity, we just add a config property > that tells root directory of all hive client, and every hive client is a > directory whose name is the hive name(default one do not need locate in). > 3、Attach only a hive to one project , so when creating a project, you should > specify a hive name, and according to it we can find the hive client(include > hive command and config files). > 4、when load table in one project, find the hive-site.xml and create a > HiveClient using this config file. > 5、can not take HCatInputFormat as inputFormat in FactDistinctColumnsJob, so > we change the job and take the intermediate hive table location as input file > and change FactDistinctColumnsMapper. HiveColumnCardinalityJob will fail if > we use additional hive. > 6、Because we need to run MR in one hadoop cluster and input or output located > at other HDFS, so when we set input location to real name node address > instead of name service(this is a config property too). > That is all we do, I think it can make things easy to manage more > than one hives and hadoops. we have apply it in our env and it works well. I > hope it can help other people... > patch uploaded, illustrations: > 1、add two config property, > 2、add hivename to projectInstance and make projectName in cube persistence in > hbase. > 3、create HiveClient with a hive-site.xml file or use default one that in > kylin classpath > 4、modify two hadoop job: FactDistinctColumnsJob and CuboidJob, take > Intermediate table name as input and change to table location in run() > 5、transform nameservice to master name node while access data located in > other hadoop if necessary. > the patch is based on 1.0-incubating and we add patchs KYLIN-1014、KYLIN-1021 > and KYLIN-957 in order .. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KYLIN-1172) kylin support multi-hive on different hadoop cluster
[ https://issues.apache.org/jira/browse/KYLIN-1172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15039621#comment-15039621 ] Shaofeng SHI commented on KYLIN-1172: - Hi Yu, yes this is a big patch, which couldn't be merged easily; We suggest dividing it into several small patches, then it will be easier for review and merge. You can create sub-tasks under this JIRA, then attache the patch file on each subtask JIRA. For now I will set the "fix version" to v1.3, as v1.2 will be released soon, hope it can be included in next release. Thanks for your contribution! > kylin support multi-hive on different hadoop cluster > > > Key: KYLIN-1172 > URL: https://issues.apache.org/jira/browse/KYLIN-1172 > Project: Kylin > Issue Type: Improvement >Affects Versions: v1.0 >Reporter: fengYu > Fix For: v1.3 > > Attachments: > 0001-support-more-hives-depend-on-different-hadoop-add-co.patch, > 0001-support-more-hives-depend-on-different-hadoop.patch > > > Hi, I recently modify kylin to support multi-hive on different hadoop > cluster and take them as input source to kylin, we do this since the > following reasons: > 1、we have more than one hadoop cluster and many hive depend on them(products > may has its own hive), we cannot migrate those hives to one and don't want to > deploy one kylin for every hive source. > 2、our hadoop cluster deploy in different DC, we need to support them in one > kylin instance. > 3、source data in hive is much less than hfile, so copy those files cross > different different is more efficient(fact distinct column job and base > cuboid job need take datas at hive as input), so we deploy hbase and hadoop > in one DC (separated in different HDFS). > So, we divide data flow into 3 parts, hive is input source, hadoop do > computing which will generate many temporary files, hbase is output. After > cube building, queries on kylin just interactive with hbase. therefore, what > we need to do is how to build cube base on differnet hives and hadoops. > Our method are summarized below : > 1、Deploy hive and hadoops, before start kylin, user should deploy all hives > and hadoop, and ensure you can run hive sql in ./hive. and access every HDFS > with 'hadoop fs 'command(add more nameservice in hdfs-site.xml). > 2、Divide hives into two part: the hive that used when kylin start(we call it > default one) and others are additional, we should allocate a name for every > hive (default one is null), For simplicity, we just add a config property > that tells root directory of all hive client, and every hive client is a > directory whose name is the hive name(default one do not need locate in). > 3、Attach only a hive to one project , so when creating a project, you should > specify a hive name, and according to it we can find the hive client(include > hive command and config files). > 4、when load table in one project, find the hive-site.xml and create a > HiveClient using this config file. > 5、can not take HCatInputFormat as inputFormat in FactDistinctColumnsJob, so > we change the job and take the intermediate hive table location as input file > and change FactDistinctColumnsMapper. HiveColumnCardinalityJob will fail if > we use additional hive. > 6、Because we need to run MR in one hadoop cluster and input or output located > at other HDFS, so when we set input location to real name node address > instead of name service(this is a config property too). > That is all we do, I think it can make things easy to manage more > than one hives and hadoops. we have apply it in our env and it works well. I > hope it can help other people... > patch uploaded, illustrations: > 1、add two config property, > 2、add hivename to projectInstance and make projectName in cube persistence in > hbase. > 3、create HiveClient with a hive-site.xml file or use default one that in > kylin classpath > 4、modify two hadoop job: FactDistinctColumnsJob and CuboidJob, take > Intermediate table name as input and change to table location in run() > 5、transform nameservice to master name node while access data located in > other hadoop if necessary. > the patch is based on 1.0-incubating and we add patchs KYLIN-1014、KYLIN-1021 > and KYLIN-957 in order .. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KYLIN-1102) Move "website" out of source code repository
[ https://issues.apache.org/jira/browse/KYLIN-1102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaofeng SHI updated KYLIN-1102: Fix Version/s: (was: v1.2) Backlog > Move "website" out of source code repository > > > Key: KYLIN-1102 > URL: https://issues.apache.org/jira/browse/KYLIN-1102 > Project: Kylin > Issue Type: Task >Affects Versions: v1.1 >Reporter: Shaofeng SHI >Assignee: Shaofeng SHI > Fix For: Backlog > > > The "website" module traces the content of kylin home page, which is not a > part of kylin source code; so we should move it out of the source git > repository. We have the following options: > 1) create an ASF svn repository > 2) create an ASF git repository > 3) create a github git repository > Personally I prefer 3) as it can be easily accessed; Please give your comment. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KYLIN-955) HiveColumnCardinalityJob didn't use configurations in conf/kylin_job_conf.xml
[ https://issues.apache.org/jira/browse/KYLIN-955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaofeng SHI updated KYLIN-955: --- Fix Version/s: (was: v1.2) Backlog > HiveColumnCardinalityJob didn't use configurations in conf/kylin_job_conf.xml > - > > Key: KYLIN-955 > URL: https://issues.apache.org/jira/browse/KYLIN-955 > Project: Kylin > Issue Type: Bug > Components: Job Engine >Affects Versions: v0.7.2, v0.7.1 >Reporter: Shaofeng SHI >Assignee: Shaofeng SHI >Priority: Minor > Fix For: Backlog > > > We defined some customized configurations in conf/kylin_job_conf.xml, while > the cardinality job doesn't use those configurations; > This job's behavior need be consistent with others like the cubing jobs; -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (KYLIN-1168) Couldn't save cube after doing some modification, get "Update data model is not allowed! Please create a new cube if needed" error
[ https://issues.apache.org/jira/browse/KYLIN-1168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaofeng SHI resolved KYLIN-1168. - Resolution: Fixed The issue has been fixed, plan to release in v1.2 > Couldn't save cube after doing some modification, get "Update data model is > not allowed! Please create a new cube if needed" error > -- > > Key: KYLIN-1168 > URL: https://issues.apache.org/jira/browse/KYLIN-1168 > Project: Kylin > Issue Type: Improvement > Components: Metadata, REST Service >Affects Versions: v1.1, v1.0 >Reporter: Shaofeng SHI >Assignee: Shaofeng SHI > Fix For: v1.2 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KYLIN-1122) Kylin support detail data query from fact table
[ https://issues.apache.org/jira/browse/KYLIN-1122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaofeng SHI updated KYLIN-1122: Fix Version/s: (was: v1.2) v1.3 Move target release to v1.3 > Kylin support detail data query from fact table > --- > > Key: KYLIN-1122 > URL: https://issues.apache.org/jira/browse/KYLIN-1122 > Project: Kylin > Issue Type: New Feature > Components: Query Engine >Affects Versions: v1.2 >Reporter: Xiaoyu Wang >Assignee: liyang > Fix For: v2.0, v1.3 > > Attachments: > 0001-KYLIN-1122-Kylin-support-detail-data-query-from-fact(2.x-staging).patch, > 0001-KYLIN-1122-Kylin-support-detail-data-query-from-fact(update-v2-1.x-staging).patch > > > Now Kylin does not support query correct detail rows from fact table like: > select column1,column2,column3 from fact_table > The jira KYLIN-1075 add the "SUM" function on the measure column if defined. > But only the column number type is support. > I change some code to support this issue: > Add a "VALUE" measure function : the same value and datatype in the input and > output of this function. > If you want to query detail data from fact table > *require*: > 1.Configure the column which not dimensions to "VALUE" or "SUM" measure.(If > not configure measure function in the column will get NULL value) > 2.The source table must has an unique value column and configure it as > dimension. > If you have the better solution please comment here. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KYLIN-1196) Prepare release v1.2
Shaofeng SHI created KYLIN-1196: --- Summary: Prepare release v1.2 Key: KYLIN-1196 URL: https://issues.apache.org/jira/browse/KYLIN-1196 Project: Kylin Issue Type: Bug Components: General Reporter: Shaofeng SHI Assignee: Shaofeng SHI -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KYLIN-1168) Couldn't save cube after doing some modification, get "Update data model is not allowed! Please create a new cube if needed" error
[ https://issues.apache.org/jira/browse/KYLIN-1168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaofeng SHI updated KYLIN-1168: Labels: QE (was: ) > Couldn't save cube after doing some modification, get "Update data model is > not allowed! Please create a new cube if needed" error > -- > > Key: KYLIN-1168 > URL: https://issues.apache.org/jira/browse/KYLIN-1168 > Project: Kylin > Issue Type: Improvement > Components: Metadata, REST Service >Affects Versions: v1.1, v1.0 >Reporter: Shaofeng SHI >Assignee: Shaofeng SHI > Labels: QE > Fix For: v1.2 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KYLIN-1161) Rest API /api/cubes?cubeName= is doing fuzzy match instead of exact match
[
https://issues.apache.org/jira/browse/KYLIN-1161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shaofeng SHI updated KYLIN-1161:
Labels: QE (was: )
> Rest API /api/cubes?cubeName= is doing fuzzy match instead of exact match
> --
>
> Key: KYLIN-1161
> URL: https://issues.apache.org/jira/browse/KYLIN-1161
> Project: Kylin
> Issue Type: Bug
> Components: REST Service
>Affects Versions: v1.1, v1.0, v0.7.2, v0.7.1, v1.1.1
>Reporter: Shaofeng SHI
>Assignee: Zhong,Jason
> Labels: QE
> Fix For: v1.2, 2.0
>
>
> This is reported by Yang HaiLe from dev mailing list:
> When I use restful api to get details of a cube, I found that the server
> will return more than one cube’s detail I want. For example:
> I use the url:
> http://server_ip:7070/kylin/api/cubes?cubeName=v5&limit=15&offset=0. The
> server will return these:
>[
> {
> "uuid": "876dd9d8-bc40-45fd-be6b-e0429ff9d4d1",
> "name": "v5",
> "owner": "ADMIN",
> "version": null,
> "cost": 50,
> "status": "READY",
> "segments": [
> {
> "uuid": "dd80cab3-1069-4333-8463-e0e48f2602c6",
> "name": "2015102000_2015102100",
> "status": "READY",
> ……….
> },
> {
> "uuid": "960e44b8-ac38-4483-8dbe-6a6a817ff4e1",
> "name": "2015102000_2015102200",
> "status": "NEW",
> ……….
> },
> {
> "uuid": "a8f6116f-acd6-46ac-be2f-021c2b291531",
> "name": "2015102100_2015102200",
> "status": "READY",
> ……….
> }
> ],
> "last_modified": 1448258568340,
> "descriptor": "v5",
> "create_time_utc": 1448244454401,
> "auto_merge_time_ranges": null,
> "retention_range": 0,
> "size_kb": 0,
> "input_records_count": 0,
> "input_records_size": 0
> },
> {
> "uuid": "c0dc404a-cfe6-4315-ac1c-ef52b27f8335",
> "name": "v5_21",
> "owner": "ADMIN",
> "version": null,
> "cost": 50,
> "status": "READY",
> "segments": [
> {
> "uuid": "c8e195ba-51a9-4fd9-be86-40e9943bcb1c",
> "name": "2015102100_2015102200",
>"status": "READY",
> ……….
> }
> ],
> "last_modified": 1448257690944,
> "descriptor": "v5_21",
> "create_time_utc": 1448247295576,
> "auto_merge_time_ranges": null,
> "retention_range": 0,
> "size_kb": 0,
> "input_records_count": 0,
> "input_records_size": 0
> }
> ]
> I don’t understand why this happen. The v5_21 cube and v5 cube base a sample
> fact table and project.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KYLIN-1140) Kylin's sample cube "kylin_sales_cube" couldn't be saved.
[ https://issues.apache.org/jira/browse/KYLIN-1140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaofeng SHI updated KYLIN-1140: Labels: QE (was: ) > Kylin's sample cube "kylin_sales_cube" couldn't be saved. > - > > Key: KYLIN-1140 > URL: https://issues.apache.org/jira/browse/KYLIN-1140 > Project: Kylin > Issue Type: Bug > Components: General >Affects Versions: v1.1, v1.0 >Reporter: Shaofeng SHI >Assignee: Shaofeng SHI > Labels: QE > Fix For: v2.0, v1.2 > > > If edit the sample cube and then click save, a NPE will be thrown and block > user to move ahead. > The root cause is In CubeController it uses the cube_des name as the cube > name to load cube instance; Usually for the cubes that created from Kylin's > UI, the desc name = cube name, so it has no problem. But for the sample > "kylin_sales_cube", its name != cube desc name. This is a bug, need to use > the accurate cube name there. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KYLIN-1121) ResourceTool download/upload does not work in binary package
[ https://issues.apache.org/jira/browse/KYLIN-1121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaofeng SHI updated KYLIN-1121: Labels: QE (was: ) > ResourceTool download/upload does not work in binary package > > > Key: KYLIN-1121 > URL: https://issues.apache.org/jira/browse/KYLIN-1121 > Project: Kylin > Issue Type: Bug >Affects Versions: v1.1 >Reporter: liyang >Assignee: liyang > Labels: QE > Fix For: v2.0, v1.2 > > > ResourceTool download/upload works in dev env, but not after deployed as > binary package. > It turns a check is by 'assert' which becomes ineffective in prod env. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KYLIN-1121) ResourceTool download/upload does not work in binary package
[ https://issues.apache.org/jira/browse/KYLIN-1121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15041189#comment-15041189 ] Shaofeng SHI commented on KYLIN-1121: - Need verify "$KYLIN_HOME/bin/metastore.sh backup" can dump metadata from HBase to local disk. > ResourceTool download/upload does not work in binary package > > > Key: KYLIN-1121 > URL: https://issues.apache.org/jira/browse/KYLIN-1121 > Project: Kylin > Issue Type: Bug >Affects Versions: v1.1 >Reporter: liyang >Assignee: liyang > Labels: QE > Fix For: v2.0, v1.2 > > > ResourceTool download/upload works in dev env, but not after deployed as > binary package. > It turns a check is by 'assert' which becomes ineffective in prod env. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KYLIN-1108) Return Type Empty When Measure-> Count In Cube Design
[ https://issues.apache.org/jira/browse/KYLIN-1108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaofeng SHI updated KYLIN-1108: Labels: QE (was: ) > Return Type Empty When Measure-> Count In Cube Design > - > > Key: KYLIN-1108 > URL: https://issues.apache.org/jira/browse/KYLIN-1108 > Project: Kylin > Issue Type: Bug > Components: Web >Affects Versions: Future > Environment: CentOS6.5+HDP2.3 >Reporter: Yiming Liu >Assignee: Zhong,Jason >Priority: Minor > Labels: QE > Fix For: v2.0, v1.2 > > > In Cube Designer, Measure Panel. > Add Measure, select "COUNT" expression, the return type is "empty". > But if select "SUM" first, then select "COUNT", the return type will be > "BIGINT". -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KYLIN-1098) two "kylin.hbase.region.count.min" in conf/kylin.properties
[ https://issues.apache.org/jira/browse/KYLIN-1098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaofeng SHI updated KYLIN-1098: Labels: QE (was: ) > two "kylin.hbase.region.count.min" in conf/kylin.properties > --- > > Key: KYLIN-1098 > URL: https://issues.apache.org/jira/browse/KYLIN-1098 > Project: Kylin > Issue Type: Bug > Components: General >Affects Versions: v1.1 >Reporter: Shaofeng SHI >Assignee: Shaofeng SHI > Labels: QE > Fix For: v1.2 > > > There are two "kylin.hbase.region.count.min" in conf/kylin.perperteis by > mistake; the second one should be "kylin.hbase.region.count.max". -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KYLIN-1078) UI - Cannot have comments in the end of New Query textbox
[ https://issues.apache.org/jira/browse/KYLIN-1078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaofeng SHI updated KYLIN-1078: Labels: QE (was: ) > UI - Cannot have comments in the end of New Query textbox > - > > Key: KYLIN-1078 > URL: https://issues.apache.org/jira/browse/KYLIN-1078 > Project: Kylin > Issue Type: Bug > Components: Web >Reporter: Dong Li >Assignee: Zhong,Jason >Priority: Minor > Labels: QE > Fix For: v2.0, v1.2 > > Attachments: > 1.x-0001-KYLIN-1078-Cannot-have-comments-in-the-end-of-New-Qu.patch, > 2.x-0001-KYLIN-1078-Cannot-have-comments-in-the-end-of-New-Qu.patch > > > 1. Navigate to http://sandbox:7070/kylin/query > 2. Input following sql into textbox: > select * from test_kylin_fact > ---comment > 3. Click Submit button > Found Errors: > Lexical error at line 2, column 23. Encountered: after : "" -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (KYLIN-1078) UI - Cannot have comments in the end of New Query textbox
[ https://issues.apache.org/jira/browse/KYLIN-1078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaofeng SHI reopened KYLIN-1078: - Reopen it, please close until the fix be released > UI - Cannot have comments in the end of New Query textbox > - > > Key: KYLIN-1078 > URL: https://issues.apache.org/jira/browse/KYLIN-1078 > Project: Kylin > Issue Type: Bug > Components: Web >Reporter: Dong Li >Assignee: Zhong,Jason >Priority: Minor > Labels: QE > Fix For: v2.0, v1.2 > > Attachments: > 1.x-0001-KYLIN-1078-Cannot-have-comments-in-the-end-of-New-Qu.patch, > 2.x-0001-KYLIN-1078-Cannot-have-comments-in-the-end-of-New-Qu.patch > > > 1. Navigate to http://sandbox:7070/kylin/query > 2. Input following sql into textbox: > select * from test_kylin_fact > ---comment > 3. Click Submit button > Found Errors: > Lexical error at line 2, column 23. Encountered: after : "" -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KYLIN-1075) select [MeasureCol] from [FactTbl] is not supported
[ https://issues.apache.org/jira/browse/KYLIN-1075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaofeng SHI updated KYLIN-1075: Labels: QE (was: ) > select [MeasureCol] from [FactTbl] is not supported > --- > > Key: KYLIN-1075 > URL: https://issues.apache.org/jira/browse/KYLIN-1075 > Project: Kylin > Issue Type: Bug > Components: Query Engine >Reporter: Dong Li >Assignee: Dong Li >Priority: Minor > Labels: QE > Fix For: v2.0, v1.2 > > Attachments: > 1.x-KYLIN-1075-select-MeasureCol-from-FactTbl-is-not-sup.patch, > 2.x-KYLIN-1075-select-MeasureCol-from-FactTbl-is-not-sup.patch > > > Input SQL: > select item_count from test_kylin_fact > Output exception: > Column DEFAULT.TEST_KYLIN_FACT.ITEM_COUNT does not exist in row key desc > while executing SQL: "select item_count from test_kylin_fact LIMIT 5" -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (KYLIN-1075) select [MeasureCol] from [FactTbl] is not supported
[ https://issues.apache.org/jira/browse/KYLIN-1075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaofeng SHI reopened KYLIN-1075: - > select [MeasureCol] from [FactTbl] is not supported > --- > > Key: KYLIN-1075 > URL: https://issues.apache.org/jira/browse/KYLIN-1075 > Project: Kylin > Issue Type: Bug > Components: Query Engine >Reporter: Dong Li >Assignee: Dong Li >Priority: Minor > Labels: QE > Fix For: v2.0, v1.2 > > Attachments: > 1.x-KYLIN-1075-select-MeasureCol-from-FactTbl-is-not-sup.patch, > 2.x-KYLIN-1075-select-MeasureCol-from-FactTbl-is-not-sup.patch > > > Input SQL: > select item_count from test_kylin_fact > Output exception: > Column DEFAULT.TEST_KYLIN_FACT.ITEM_COUNT does not exist in row key desc > while executing SQL: "select item_count from test_kylin_fact LIMIT 5" -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KYLIN-1070) changing case in table name in model desc
[ https://issues.apache.org/jira/browse/KYLIN-1070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaofeng SHI updated KYLIN-1070: Labels: QE (was: ) > changing case in table name in model desc > --- > > Key: KYLIN-1070 > URL: https://issues.apache.org/jira/browse/KYLIN-1070 > Project: Kylin > Issue Type: Bug > Components: Job Engine >Affects Versions: v1.1, 1.x-HBase1.1.3 >Reporter: vipin >Assignee: Shaofeng SHI >Priority: Minor > Labels: QE > Fix For: v1.2 > > Attachments: kylin_1070.patch > > > with v1.1-release version lets say if i am sending cube request having table > name in camel case > ,its get persisted and in package org.apache.kylin.job.JoinedFlatTable > map returned by private static Map > buildTableAliasMap(DataModelDesc dataModelDesc) method > has camel case table name as send from request, while IntermediateColumnDesc > has upper case table names > table name which we get from intermediateTableDesc.getDataModel() is same as > request while > intermediateTableDesc.getColumnList() has upper case table name > I have checked in hbase : > get 'kylin_metadata' ,'/model_desc/TestSimple_114.json' -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KYLIN-1069) update tip for 'Partition Column' on UI
[ https://issues.apache.org/jira/browse/KYLIN-1069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaofeng SHI updated KYLIN-1069: Labels: QE (was: ) > update tip for 'Partition Column' on UI > --- > > Key: KYLIN-1069 > URL: https://issues.apache.org/jira/browse/KYLIN-1069 > Project: Kylin > Issue Type: Improvement > Components: Web >Affects Versions: v2.0, v1.1 >Reporter: Zhong,Jason >Assignee: Zhong,Jason > Labels: QE > Fix For: v2.0, v1.2 > > > when design Cube or Model on ui ,for 'Partition Column', > >Partition column will select 'date' type column from fact table > need to update the this tip in wizard. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KYLIN-1058) Remove "right join" during model creation
[ https://issues.apache.org/jira/browse/KYLIN-1058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaofeng SHI updated KYLIN-1058: Labels: QE (was: ) > Remove "right join" during model creation > - > > Key: KYLIN-1058 > URL: https://issues.apache.org/jira/browse/KYLIN-1058 > Project: Kylin > Issue Type: Bug >Reporter: liyang >Assignee: Zhong,Jason > Labels: QE > Fix For: v2.0, v1.2 > > > I don't think Kylin support "right join" (in addition to inner join and left > join). Remove it in model creation options. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KYLIN-1039) Filter like (A or false) yields wrong result
[
https://issues.apache.org/jira/browse/KYLIN-1039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shaofeng SHI updated KYLIN-1039:
Labels: QE (was: )
> Filter like (A or false) yields wrong result
>
>
> Key: KYLIN-1039
> URL: https://issues.apache.org/jira/browse/KYLIN-1039
> Project: Kylin
> Issue Type: Bug
> Components: Query Engine
>Affects Versions: v1.0
>Reporter: Dayue Gao
> Labels: QE
> Fix For: v2.0, v1.2
>
> Attachments: KYLIN-1039-1.x-staging.patch
>
>
> The following query on test dataset produces a result set containing 5 rows.
> {code:sql}
> select test_cal_dt.week_beg_dt, sum(price) as GMV
> from test_kylin_fact
> inner JOIN edw.test_cal_dt as test_cal_dt ON test_kylin_fact.cal_dt =
> test_cal_dt.cal_dt
> where test_cal_dt.week_beg_dt between DATE '2013-09-01' and DATE
> '2013-10-01' and lstg_format_name='FP-GTC'
> group by test_cal_dt.week_beg_dt
> {code}
> However, if I change the where condition to the following, Kylin produces
> empty result. This is wrong because `A or false` is just `A`, the result
> should be the same as above qeury.
> {code:sql}
> where test_cal_dt.week_beg_dt between DATE '2013-09-01' and DATE
> '2013-10-01' and (lstg_format_name='FP-GTC' or 'a' = 'b')
> {code}
> I have tried to add a constant folding rule
> `ReduceExpressionsRule.FILTER_INSTANCE` from calcite, expecting planner to
> reduce the second query to the first one. But it didn't work. Seems the rule
> has bug in itself, see https://issues.apache.org/jira/browse/DRILL-2218.
> As as result, we need more investigating to see why it goes wrong and fix the
> problem.
> BTW, the second query may seems rediculous at first glance. But in fact this
> kind of query is generated by one of our reporting front-end.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KYLIN-1033) Error when joining two sub-queries
[ https://issues.apache.org/jira/browse/KYLIN-1033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaofeng SHI updated KYLIN-1033: Labels: QE (was: ) > Error when joining two sub-queries > -- > > Key: KYLIN-1033 > URL: https://issues.apache.org/jira/browse/KYLIN-1033 > Project: Kylin > Issue Type: Bug >Affects Versions: v1.0 >Reporter: liyang >Assignee: liyang > Labels: QE > Fix For: v2.0, v1.2 > > Attachments: > 1.x-0001-KYLIN-1033-Error-when-joining-two-sub-queries.patch, > 2.x-0001-KYLIN-1033-Error-when-joining-two-sub-queries.patch > > > Copy from mail list: > 奔跑的蜗牛 99089...@qq.com via apache.org > We create two cubes in one project. We want to join the two query (querying > data from two cube) together. > But we got the error : > null while executing SQL: "with a as ( select part_dt,sum(price) amount from > kylin_sales group by part_dt ), b as (select part_dt,count(price) cn from > kylin_sales group by part_dt) select * from a join b on a.part_dt= b.part_dt > LIMIT 5" > The example for learn_kylin as following. > We can get data using query select * from a , select * from b . But when > join together,we get error. > with a as ( > select part_dt,sum(price) amount > from kylin_sales > group by part_dt ), > b as (select part_dt,count(price) cn > from kylin_sales > group by part_dt) > --select * from a > --select * from b > select * from a > join b on a.part_dt= b.part_dt -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KYLIN-1033) Error when joining two sub-queries
[ https://issues.apache.org/jira/browse/KYLIN-1033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaofeng SHI updated KYLIN-1033: Affects Version/s: v1.1 > Error when joining two sub-queries > -- > > Key: KYLIN-1033 > URL: https://issues.apache.org/jira/browse/KYLIN-1033 > Project: Kylin > Issue Type: Bug >Affects Versions: v1.1, v1.0 >Reporter: liyang >Assignee: liyang > Labels: QE > Fix For: v2.0, v1.2 > > Attachments: > 1.x-0001-KYLIN-1033-Error-when-joining-two-sub-queries.patch, > 2.x-0001-KYLIN-1033-Error-when-joining-two-sub-queries.patch > > > Copy from mail list: > 奔跑的蜗牛 99089...@qq.com via apache.org > We create two cubes in one project. We want to join the two query (querying > data from two cube) together. > But we got the error : > null while executing SQL: "with a as ( select part_dt,sum(price) amount from > kylin_sales group by part_dt ), b as (select part_dt,count(price) cn from > kylin_sales group by part_dt) select * from a join b on a.part_dt= b.part_dt > LIMIT 5" > The example for learn_kylin as following. > We can get data using query select * from a , select * from b . But when > join together,we get error. > with a as ( > select part_dt,sum(price) amount > from kylin_sales > group by part_dt ), > b as (select part_dt,count(price) cn > from kylin_sales > group by part_dt) > --select * from a > --select * from b > select * from a > join b on a.part_dt= b.part_dt -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KYLIN-989) column width is too narrow for timestamp field
[ https://issues.apache.org/jira/browse/KYLIN-989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaofeng SHI updated KYLIN-989: --- Labels: QE (was: ) > column width is too narrow for timestamp field > -- > > Key: KYLIN-989 > URL: https://issues.apache.org/jira/browse/KYLIN-989 > Project: Kylin > Issue Type: Bug > Components: Web >Affects Versions: v1.0 >Reporter: Zhong,Jason >Assignee: Zhong,Jason >Priority: Minor > Labels: QE > Fix For: v1.2 > > Attachments: Screen Shot.png > > > in query page, query result column width is too narrow for timestamp field -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KYLIN-966) When user creates a cube, if enter a name which already exists, Kylin will thrown expection on last step
[ https://issues.apache.org/jira/browse/KYLIN-966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaofeng SHI updated KYLIN-966: --- Labels: QE (was: ) > When user creates a cube, if enter a name which already exists, Kylin will > thrown expection on last step > > > Key: KYLIN-966 > URL: https://issues.apache.org/jira/browse/KYLIN-966 > Project: Kylin > Issue Type: Bug > Components: Web >Affects Versions: v0.7.2 >Reporter: Shaofeng SHI >Assignee: Zhong,Jason > Labels: QE > Fix For: v1.2 > > Attachments: KYLIN-966.patch > > > Kylin cube wizard should check the uniqueness of the name once user entered > it; Otherwise, it will fail on last step when writting to resource store > (timestamp wasn' expected); And even if user changes name will not work, > finally have to cancel and create from scratch, which is bad. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KYLIN-930) can't see realizations under each project at project list page
[ https://issues.apache.org/jira/browse/KYLIN-930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaofeng SHI updated KYLIN-930: --- Labels: QE (was: ) > can't see realizations under each project at project list page > -- > > Key: KYLIN-930 > URL: https://issues.apache.org/jira/browse/KYLIN-930 > Project: Kylin > Issue Type: Bug > Components: Web >Affects Versions: v0.7.2 >Reporter: Zhong,Jason >Assignee: Zhong,Jason > Labels: QE > Fix For: v1.2 > > Attachments: > 0001-KYLIN-930-list-cube-realization-under-each-project.patch > > > at project list page. > under each project ,we should see all cubes . > due to backend data structure change ,frontend can't see it now. > need to update it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KYLIN-389) Can't edit cube name for existing cubes
[ https://issues.apache.org/jira/browse/KYLIN-389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaofeng SHI updated KYLIN-389: --- Labels: QE github-import (was: github-import) > Can't edit cube name for existing cubes > --- > > Key: KYLIN-389 > URL: https://issues.apache.org/jira/browse/KYLIN-389 > Project: Kylin > Issue Type: Improvement > Components: Web >Affects Versions: v0.7.1 >Reporter: Luke Han >Assignee: Zhong,Jason > Labels: QE, github-import > Fix For: v1.2 > > > Once cube be created, the _cube name_ can't be edit again. > Imported from GitHub > Url: https://github.com/KylinOLAP/Kylin/issues/116 > Created by: [janzhongi|https://github.com/janzhongi] > Labels: enhancement, > Milestone: Backlog > Created at: Wed Nov 26 17:01:55 CST 2014 > State: open -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KYLIN-391) The width of the result table can not be stretched
[ https://issues.apache.org/jira/browse/KYLIN-391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaofeng SHI updated KYLIN-391: --- Labels: QE github-import (was: github-import) > The width of the result table can not be stretched > -- > > Key: KYLIN-391 > URL: https://issues.apache.org/jira/browse/KYLIN-391 > Project: Kylin > Issue Type: Wish > Components: Web >Reporter: Luke Han >Assignee: Zhong,Jason > Labels: QE, github-import > Fix For: v1.2 > > > After query, the result is showed in table. But the width of the table can > not be stretched. > for example, the url column can't full display > ![034642df-725f-46b0-b413-c47f717c1694|https://cloud.githubusercontent.com/assets/4865304/5197648/a4b78286-7580-11e4-8b1c-c3388e66464a.png] > Imported from GitHub > Url: https://github.com/KylinOLAP/Kylin/issues/114 > Created by: [corndolly|https://github.com/corndolly] > Labels: enhancement, > Milestone: Backlog > Assignee: [lukehan|https://github.com/lukehan] > Created at: Wed Nov 26 15:27:04 CST 2014 > State: open -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KYLIN-930) can't see realizations under each project at project list page
[ https://issues.apache.org/jira/browse/KYLIN-930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15041315#comment-15041315 ] Shaofeng SHI commented on KYLIN-930: Patch merged in 1.x-staging and 2.x-staging branch; I verified it works on 1.x; Thanks Jia's contribution; On 2.x seems the link on a project isn't working, Jason please double check it, thanks! > can't see realizations under each project at project list page > -- > > Key: KYLIN-930 > URL: https://issues.apache.org/jira/browse/KYLIN-930 > Project: Kylin > Issue Type: Bug > Components: Web >Affects Versions: v0.7.2 >Reporter: Zhong,Jason >Assignee: Zhong,Jason > Labels: QE > Fix For: v1.2 > > Attachments: > 0001-KYLIN-930-list-cube-realization-under-each-project.patch > > > at project list page. > under each project ,we should see all cubes . > due to backend data structure change ,frontend can't see it now. > need to update it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KYLIN-1203) Cannot save cube after correcting the configuration mistake
[ https://issues.apache.org/jira/browse/KYLIN-1203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15046254#comment-15046254 ] Shaofeng SHI commented on KYLIN-1203: - Good catch Lola and Dong; Discussed it with Jason today, the front-end of the data model info wasn't flush when error occurs, Jason will fix it in 1.x at first, then check 2.x. > Cannot save cube after correcting the configuration mistake > --- > > Key: KYLIN-1203 > URL: https://issues.apache.org/jira/browse/KYLIN-1203 > Project: Kylin > Issue Type: Bug >Affects Versions: v1.2 >Reporter: Lola Liu >Assignee: Zhong,Jason > > STEPS: > 1. Modify cube, add 2 count(which will cause save error). > 2. Save cube and got save error caused by 2 count > 3. Go to pre and correct the count mistake > 4. Save > RESULT: > 4. Error Message > Failed to deal with the request: Overwriting conflict > /model_desc/test_test.json, expect old TS 1449478829188, but it is > 1449478590889 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KYLIN-1206) Support "UNION" in query
Shaofeng SHI created KYLIN-1206: --- Summary: Support "UNION" in query Key: KYLIN-1206 URL: https://issues.apache.org/jira/browse/KYLIN-1206 Project: Kylin Issue Type: Wish Components: Query Engine Affects Versions: v1.1.1, v0.7.1, v0.7.2 Reporter: Shaofeng SHI Assignee: liyang Fix For: Backlog Kylin doesn't support UNION in SQL query now, this should be implemented. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KYLIN-1219) Kylin support SSO with Spring SAML
Shaofeng SHI created KYLIN-1219: --- Summary: Kylin support SSO with Spring SAML Key: KYLIN-1219 URL: https://issues.apache.org/jira/browse/KYLIN-1219 Project: Kylin Issue Type: New Feature Components: REST Service Reporter: Shaofeng SHI Assignee: Shaofeng SHI Fix For: v2.1 Besides LDAP, SSO is widely adopted by enterprises for user authentication; As Kylin rest service is implemented with Spring security framework, it is natural to implement SSO with SAML 2.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KYLIN-1221) Allow user to kill Hadoop job in the job list page
[ https://issues.apache.org/jira/browse/KYLIN-1221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaofeng SHI updated KYLIN-1221: Labels: newbie (was: ) Fix Version/s: Backlog > Allow user to kill Hadoop job in the job list page > -- > > Key: KYLIN-1221 > URL: https://issues.apache.org/jira/browse/KYLIN-1221 > Project: Kylin > Issue Type: Wish > Components: Job Engine >Affects Versions: v1.1, v1.0, v0.7.2, v0.7.1 >Reporter: Shaofeng SHI >Assignee: ZhouQianhao > Labels: newbie > Fix For: Backlog > > > Sometimes user expects to abondon the current running hadoop job, he can > choose to kill the related job directly from the Kylin job page, instead of > manually run yarn or mapred CLI to kill it. > Besides, when user discards a Kylin job, the underlying running hadoop job > should also be killed automatically, to release the computing resources in > time. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KYLIN-1221) Allow user to kill Hadoop job in the job list page
Shaofeng SHI created KYLIN-1221: --- Summary: Allow user to kill Hadoop job in the job list page Key: KYLIN-1221 URL: https://issues.apache.org/jira/browse/KYLIN-1221 Project: Kylin Issue Type: Wish Components: Job Engine Affects Versions: v0.7.1, v0.7.2, v1.0, v1.1 Reporter: Shaofeng SHI Assignee: ZhouQianhao Sometimes user expects to abondon the current running hadoop job, he can choose to kill the related job directly from the Kylin job page, instead of manually run yarn or mapred CLI to kill it. Besides, when user discards a Kylin job, the underlying running hadoop job should also be killed automatically, to release the computing resources in time. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KYLIN-1078) UI - Cannot have comments in the end of New Query textbox
[ https://issues.apache.org/jira/browse/KYLIN-1078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaofeng SHI updated KYLIN-1078: Fix Version/s: (was: v1.2) v1.3 It need additional processing for keyword "limit" which appears in comment part. Move this to v1.3. > UI - Cannot have comments in the end of New Query textbox > - > > Key: KYLIN-1078 > URL: https://issues.apache.org/jira/browse/KYLIN-1078 > Project: Kylin > Issue Type: Bug > Components: Web >Reporter: Dong Li >Assignee: Zhong,Jason >Priority: Minor > Labels: QE > Fix For: v2.0, v1.3 > > Attachments: > 1.x-0001-KYLIN-1078-Cannot-have-comments-in-the-end-of-New-Qu.patch, > 2.x-0001-KYLIN-1078-Cannot-have-comments-in-the-end-of-New-Qu.patch > > > 1. Navigate to http://sandbox:7070/kylin/query > 2. Input following sql into textbox: > select * from test_kylin_fact > ---comment > 3. Click Submit button > Found Errors: > Lexical error at line 2, column 23. Encountered: after : "" -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KYLIN-1078) UI - Cannot have comments in the end of New Query textbox
[ https://issues.apache.org/jira/browse/KYLIN-1078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaofeng SHI updated KYLIN-1078: Assignee: Dong Li (was: Zhong,Jason) > UI - Cannot have comments in the end of New Query textbox > - > > Key: KYLIN-1078 > URL: https://issues.apache.org/jira/browse/KYLIN-1078 > Project: Kylin > Issue Type: Bug > Components: Web >Reporter: Dong Li >Assignee: Dong Li >Priority: Minor > Labels: QE > Fix For: v2.0, v1.3 > > Attachments: > 1.x-0001-KYLIN-1078-Cannot-have-comments-in-the-end-of-New-Qu.patch, > 2.x-0001-KYLIN-1078-Cannot-have-comments-in-the-end-of-New-Qu.patch > > > 1. Navigate to http://sandbox:7070/kylin/query > 2. Input following sql into textbox: > select * from test_kylin_fact > ---comment > 3. Click Submit button > Found Errors: > Lexical error at line 2, column 23. Encountered: after : "" -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KYLIN-989) column width is too narrow for timestamp field
[ https://issues.apache.org/jira/browse/KYLIN-989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaofeng SHI updated KYLIN-989: --- Fix Version/s: (was: v1.2) v1.3 > column width is too narrow for timestamp field > -- > > Key: KYLIN-989 > URL: https://issues.apache.org/jira/browse/KYLIN-989 > Project: Kylin > Issue Type: Bug > Components: Web >Affects Versions: v1.0 >Reporter: Zhong,Jason >Assignee: Zhong,Jason >Priority: Minor > Labels: QE > Fix For: v1.3 > > Attachments: Screen Shot.png, not fixed.png > > > in query page, query result column width is too narrow for timestamp field -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KYLIN-391) The width of the result table can not be stretched
[ https://issues.apache.org/jira/browse/KYLIN-391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaofeng SHI updated KYLIN-391: --- Fix Version/s: (was: v1.2) v1.3 Move to v1.3 > The width of the result table can not be stretched > -- > > Key: KYLIN-391 > URL: https://issues.apache.org/jira/browse/KYLIN-391 > Project: Kylin > Issue Type: Wish > Components: Web >Reporter: Luke Han >Assignee: Zhong,Jason > Labels: QE, github-import > Fix For: v1.3 > > > After query, the result is showed in table. But the width of the table can > not be stretched. > for example, the url column can't full display > ![034642df-725f-46b0-b413-c47f717c1694|https://cloud.githubusercontent.com/assets/4865304/5197648/a4b78286-7580-11e4-8b1c-c3388e66464a.png] > Imported from GitHub > Url: https://github.com/KylinOLAP/Kylin/issues/114 > Created by: [corndolly|https://github.com/corndolly] > Labels: enhancement, > Milestone: Backlog > Assignee: [lukehan|https://github.com/lukehan] > Created at: Wed Nov 26 15:27:04 CST 2014 > State: open -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KYLIN-989) column width is too narrow for timestamp field
[ https://issues.apache.org/jira/browse/KYLIN-989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15055545#comment-15055545 ] Shaofeng SHI commented on KYLIN-989: Thanks for the checking; Set it to v1.3 > column width is too narrow for timestamp field > -- > > Key: KYLIN-989 > URL: https://issues.apache.org/jira/browse/KYLIN-989 > Project: Kylin > Issue Type: Bug > Components: Web >Affects Versions: v1.0 >Reporter: Zhong,Jason >Assignee: Zhong,Jason >Priority: Minor > Labels: QE > Fix For: v1.3 > > Attachments: Screen Shot.png, not fixed.png > > > in query page, query result column width is too narrow for timestamp field -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KYLIN-1229) CubeMigrationCLI should not need set KYLIN_HOME
Shaofeng SHI created KYLIN-1229:
---
Summary: CubeMigrationCLI should not need set KYLIN_HOME
Key: KYLIN-1229
URL: https://issues.apache.org/jira/browse/KYLIN-1229
Project: Kylin
Issue Type: Bug
Affects Versions: v1.0, v1.1, v1.2
Reporter: Shaofeng SHI
Assignee: Shaofeng SHI
Priority: Minor
Fix For: v1.3
When release a cube from one Kylin server to another Kylin server, if didn't
set KYLIN_HOME environment variable, it will throw exception:
{code}
hbase -Dlog4j.configuration=/conf/log4j.properties
org.apache.hadoop.util.RunJar lib/kylin-job-1.2-SNAPSHOT.jar
org.apache.kylin.job.tools.CubeMigrationCLI kylin-qa:80 kylin-prod:80
CUBE_NAME PROJ_NAME true true false
L4J [2015-12-14
00:44:53,578][ERROR][org.apache.kylin.common.persistence.ResourceStore] -
Create new store instance failed
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
at
org.apache.kylin.common.persistence.ResourceStore.getStore(ResourceStore.java:76)
at
org.apache.kylin.job.tools.CubeMigrationCLI.moveCube(CubeMigrationCLI.java:94)
at
org.apache.kylin.job.tools.CubeMigrationCLI.moveCube(CubeMigrationCLI.java:138)
at
org.apache.kylin.job.tools.CubeMigrationCLI.main(CubeMigrationCLI.java:82)
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.apache.hadoop.util.RunJar.main(RunJar.java:212)
Caused by: java.lang.RuntimeException: Didn't find KYLIN_CONF or KYLIN_HOME,
please set one of them
at
org.apache.kylin.common.KylinConfig.getKylinProperties(KylinConfig.java:600)
at
org.apache.kylin.common.KylinConfig.getKylinPropertiesAsInputSteam(KylinConfig.java:608)
at
org.apache.kylin.common.KylinConfig.loadKylinConfig(KylinConfig.java:249)
at
org.apache.kylin.common.KylinConfig.getInstanceFromEnv(KylinConfig.java:145)
at
org.apache.kylin.common.util.HadoopUtil.getCurrentHBaseConfiguration(HadoopUtil.java:56)
at
org.apache.kylin.common.persistence.HBaseConnection.get(HBaseConnection.java:68)
at
org.apache.kylin.common.persistence.HBaseResourceStore.getConnection(HBaseResourceStore.java:81)
at
org.apache.kylin.common.persistence.HBaseResourceStore.createHTableIfNeeded(HBaseResourceStore.java:100)
at
org.apache.kylin.common.persistence.HBaseResourceStore.(HBaseResourceStore.java:95)
... 13 more
Exception in thread "main" java.lang.IllegalArgumentException: Failed to find
metadata store by url: kylin_metadata_qa@hbase
at
org.apache.kylin.common.persistence.ResourceStore.getStore(ResourceStore.java:91)
at
org.apache.kylin.job.tools.CubeMigrationCLI.moveCube(CubeMigrationCLI.java:94)
at
org.apache.kylin.job.tools.CubeMigrationCLI.moveCube(CubeMigrationCLI.java:138)
at
org.apache.kylin.job.tools.CubeMigrationCLI.main(CubeMigrationCLI.java:82)
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)
{code}
The problem is between HBaseResourceStore.getConnection() and
HBaseConnection.get(url), which depends on an implicit KylinConfig, insteading
using the given KylinConfig.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (KYLIN-1230) When CubeMigrationCLI copied ACL from one env to another, it may not work
Shaofeng SHI created KYLIN-1230: --- Summary: When CubeMigrationCLI copied ACL from one env to another, it may not work Key: KYLIN-1230 URL: https://issues.apache.org/jira/browse/KYLIN-1230 Project: Kylin Issue Type: Bug Reporter: Shaofeng SHI Assignee: Shaofeng SHI Found an issue when using CubeMigrationCLI to migrate a cube from QA to production if selecting “copyACL” as true (this is a newly added feature). The root cause is the project in production has a different uuid as it in QA. The cube’s ACL refers to its parent by uuid. Then if a cube’s ACL is copied from QA, it couldn't find the parent, then an error is thrown. To fix the issue, it should copy the project (if it doesn't exist in the target env), or give up copy ACL when detecting the project uuid is different (and remind user to manually update ACL). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KYLIN-1230) When CubeMigrationCLI copied ACL from one env to another, it may not work
[ https://issues.apache.org/jira/browse/KYLIN-1230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaofeng SHI updated KYLIN-1230: Affects Version/s: v1.2 Fix Version/s: v1.3 Component/s: Client - CLI > When CubeMigrationCLI copied ACL from one env to another, it may not work > - > > Key: KYLIN-1230 > URL: https://issues.apache.org/jira/browse/KYLIN-1230 > Project: Kylin > Issue Type: Bug > Components: Client - CLI >Affects Versions: v1.2 >Reporter: Shaofeng SHI >Assignee: Shaofeng SHI > Fix For: v1.3 > > > Found an issue when using CubeMigrationCLI to migrate a cube from QA to > production if selecting “copyACL” as true (this is a newly added feature). > The root cause is the project in production has a different uuid as it in QA. > The cube’s ACL refers to its parent by uuid. Then if a cube’s ACL is copied > from QA, it couldn't find the parent, then an error is thrown. > To fix the issue, it should copy the project (if it doesn't exist in the > target env), or give up copy ACL when detecting the project uuid is different > (and remind user to manually update ACL). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (KYLIN-930) can't see realizations under each project at project list page
[ https://issues.apache.org/jira/browse/KYLIN-930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaofeng SHI resolved KYLIN-930. Resolution: Fixed > can't see realizations under each project at project list page > -- > > Key: KYLIN-930 > URL: https://issues.apache.org/jira/browse/KYLIN-930 > Project: Kylin > Issue Type: Bug > Components: Web >Affects Versions: v1.1, v1.0, v0.7.2 >Reporter: Zhong,Jason >Assignee: Zhong,Jason > Labels: QE > Fix For: v2.0, v1.2 > > Attachments: > 0001-KYLIN-930-list-cube-realization-under-each-project.patch > > > at project list page. > under each project ,we should see all cubes . > due to backend data structure change ,frontend can't see it now. > need to update it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (KYLIN-1070) changing case in table name in model desc
[ https://issues.apache.org/jira/browse/KYLIN-1070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaofeng SHI resolved KYLIN-1070. - Resolution: Fixed > changing case in table name in model desc > --- > > Key: KYLIN-1070 > URL: https://issues.apache.org/jira/browse/KYLIN-1070 > Project: Kylin > Issue Type: Bug > Components: Job Engine >Affects Versions: v1.1, 1.x-HBase1.1.3 >Reporter: vipin >Assignee: Shaofeng SHI >Priority: Minor > Labels: QE > Fix For: v1.2 > > Attachments: kylin_1070.patch > > > with v1.1-release version lets say if i am sending cube request having table > name in camel case > ,its get persisted and in package org.apache.kylin.job.JoinedFlatTable > map returned by private static Map > buildTableAliasMap(DataModelDesc dataModelDesc) method > has camel case table name as send from request, while IntermediateColumnDesc > has upper case table names > table name which we get from intermediateTableDesc.getDataModel() is same as > request while > intermediateTableDesc.getColumnList() has upper case table name > I have checked in hbase : > get 'kylin_metadata' ,'/model_desc/TestSimple_114.json' -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KYLIN-1075) select [MeasureCol] from [FactTbl] is not supported
[ https://issues.apache.org/jira/browse/KYLIN-1075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaofeng SHI updated KYLIN-1075: Fix Version/s: (was: v1.2) v1.3 Move to v1.3, Dong please check the issue that Lola described. > select [MeasureCol] from [FactTbl] is not supported > --- > > Key: KYLIN-1075 > URL: https://issues.apache.org/jira/browse/KYLIN-1075 > Project: Kylin > Issue Type: Bug > Components: Query Engine >Reporter: Dong Li >Assignee: Dong Li >Priority: Minor > Labels: QE > Fix For: v2.0, v1.3 > > Attachments: > 1.x-KYLIN-1075-select-MeasureCol-from-FactTbl-is-not-sup.patch, > 2.x-KYLIN-1075-select-MeasureCol-from-FactTbl-is-not-sup.patch > > > Input SQL: > select item_count from test_kylin_fact > Output exception: > Column DEFAULT.TEST_KYLIN_FACT.ITEM_COUNT does not exist in row key desc > while executing SQL: "select item_count from test_kylin_fact LIMIT 5" -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (KYLIN-1166) CubeMigrationCLI should disable and purge the cube in source store after be migrated
[ https://issues.apache.org/jira/browse/KYLIN-1166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaofeng SHI resolved KYLIN-1166. - Resolution: Fixed The change has been made and tested in our environment. Mark as fixed. > CubeMigrationCLI should disable and purge the cube in source store after be > migrated > > > Key: KYLIN-1166 > URL: https://issues.apache.org/jira/browse/KYLIN-1166 > Project: Kylin > Issue Type: Improvement > Components: Client - CLI >Affects Versions: v1.1, v1.0 >Reporter: Shaofeng SHI >Assignee: Shaofeng SHI >Priority: Minor > Fix For: v1.2 > > > As the title describes, the CubeMigrationCLI should disable/purge a cube > after it be released to another environment, to avoid a cube in ready status > in both sides. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KYLIN-1216) Can't parse DateFormat like 'YYYYMMDD' correctly in query
[
https://issues.apache.org/jira/browse/KYLIN-1216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shaofeng SHI updated KYLIN-1216:
Fix Version/s: (was: 2.0)
(was: 1.2)
v1.2
v2.0
> Can't parse DateFormat like 'MMDD' correctly in query
> -
>
> Key: KYLIN-1216
> URL: https://issues.apache.org/jira/browse/KYLIN-1216
> Project: Kylin
> Issue Type: Bug
> Components: Query Engine
>Affects Versions: 1.2, 2.0
>Reporter: Yerui Sun
>Assignee: Yerui Sun
> Fix For: v2.0, v1.2
>
> Attachments: KYLIN-1216-1.x-staging.patch,
> KYLIN-1216-2.x-staging.patch
>
>
> Kylin has support date format as 'MMDD' since KYLIN-1101, and could read
> data and build cube successfully with this format.
> However, the query sql contains " dt='20151208' " can't be parsed, the reason
> is HBaseKeyRange.initPartitionRange still using default format '-MM-DD'
> only, not read from partition desc.
> Here's the trace:
> {code}
> Caused by: java.lang.IllegalArgumentException: '20150901' is not a valid date
> of pattern '-MM-dd'
> at
> org.apache.kylin.common.util.DateFormat.stringToDate(DateFormat.java:78)
> at
> org.apache.kylin.common.util.DateFormat.stringToDate(DateFormat.java:70)
> at
> org.apache.kylin.storage.hbase.HBaseKeyRange.initPartitionRange(HBaseKeyRange.java:148)
> at
> org.apache.kylin.storage.hbase.HBaseKeyRange.init(HBaseKeyRange.java:127)
> at
> org.apache.kylin.storage.hbase.HBaseKeyRange.(HBaseKeyRange.java:101)
> at
> org.apache.kylin.storage.hbase.CubeStorageEngine.buildScanRanges(CubeStorageEngine.java:410)
> at
> org.apache.kylin.storage.hbase.CubeStorageEngine.search(CubeStorageEngine.java:134)
> at
> org.apache.kylin.query.enumerator.CubeEnumerator.queryStorage(CubeEnumerator.java:149)
> at
> org.apache.kylin.query.enumerator.CubeEnumerator.moveNext(CubeEnumerator.java:74)
> at Baz$1$1.moveNext(Unknown Source)
> at
> org.apache.calcite.linq4j.EnumerableDefaults.groupBy_(EnumerableDefaults.java:737)
> at
> org.apache.calcite.linq4j.EnumerableDefaults.groupBy(EnumerableDefaults.java:677)
> at
> org.apache.calcite.linq4j.DefaultEnumerable.groupBy(DefaultEnumerable.java:301)
> at Baz.bind(Unknown Source)
> at
> org.apache.calcite.jdbc.CalcitePrepare$CalciteSignature.enumerable(CalcitePrepare.java:281)
> at
> org.apache.calcite.jdbc.CalciteConnectionImpl.enumerable(CalciteConnectionImpl.java:235)
> at
> org.apache.calcite.jdbc.CalciteMetaImpl.createIterable(CalciteMetaImpl.java:533)
> at
> org.apache.calcite.avatica.AvaticaResultSet.execute(AvaticaResultSet.java:184)
> at
> org.apache.calcite.jdbc.CalciteResultSet.execute(CalciteResultSet.java:63)
> at
> org.apache.calcite.jdbc.CalciteResultSet.execute(CalciteResultSet.java:42)
> at
> org.apache.calcite.avatica.AvaticaConnection$1.execute(AvaticaConnection.java:473)
> at
> org.apache.calcite.jdbc.CalciteMetaImpl.prepareAndExecute(CalciteMetaImpl.java:566)
> at
> org.apache.calcite.avatica.AvaticaConnection.prepareAndExecuteInternal(AvaticaConnection.java:477)
> at
> org.apache.calcite.avatica.AvaticaStatement.executeInternal(AvaticaStatement.java:109)
> ... 83 more
> Caused by: java.text.ParseException: Unparseable date: "20150901"
> at java.text.DateFormat.parse(DateFormat.java:366)
> at
> org.apache.kylin.common.util.DateFormat.stringToDate(DateFormat.java:76)
> ... 106 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KYLIN-1203) Cannot save cube after correcting the configuration mistake
[ https://issues.apache.org/jira/browse/KYLIN-1203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaofeng SHI updated KYLIN-1203: Fix Version/s: (was: 1.2) v1.2 > Cannot save cube after correcting the configuration mistake > --- > > Key: KYLIN-1203 > URL: https://issues.apache.org/jira/browse/KYLIN-1203 > Project: Kylin > Issue Type: Bug >Affects Versions: v1.2 >Reporter: Lola Liu >Assignee: Zhong,Jason > Fix For: v1.2 > > > STEPS: > 1. Modify cube, add 2 count(which will cause save error). > 2. Save cube and got save error caused by 2 count > 3. Go to pre and correct the count mistake > 4. Save > RESULT: > 4. Error Message > Failed to deal with the request: Overwriting conflict > /model_desc/test_test.json, expect old TS 1449478829188, but it is > 1449478590889 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KYLIN-1161) Rest API /api/cubes?cubeName= is doing fuzzy match instead of exact match
[
https://issues.apache.org/jira/browse/KYLIN-1161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shaofeng SHI updated KYLIN-1161:
Issue Type: Improvement (was: Bug)
> Rest API /api/cubes?cubeName= is doing fuzzy match instead of exact match
> --
>
> Key: KYLIN-1161
> URL: https://issues.apache.org/jira/browse/KYLIN-1161
> Project: Kylin
> Issue Type: Improvement
> Components: REST Service
>Affects Versions: v1.1, v1.0, v0.7.2, v0.7.1, v1.1.1
>Reporter: Shaofeng SHI
>Assignee: Zhong,Jason
> Labels: QE
> Fix For: v1.2, 2.0
>
>
> This is reported by Yang HaiLe from dev mailing list:
> When I use restful api to get details of a cube, I found that the server
> will return more than one cube’s detail I want. For example:
> I use the url:
> http://server_ip:7070/kylin/api/cubes?cubeName=v5&limit=15&offset=0. The
> server will return these:
>[
> {
> "uuid": "876dd9d8-bc40-45fd-be6b-e0429ff9d4d1",
> "name": "v5",
> "owner": "ADMIN",
> "version": null,
> "cost": 50,
> "status": "READY",
> "segments": [
> {
> "uuid": "dd80cab3-1069-4333-8463-e0e48f2602c6",
> "name": "2015102000_2015102100",
> "status": "READY",
> ……….
> },
> {
> "uuid": "960e44b8-ac38-4483-8dbe-6a6a817ff4e1",
> "name": "2015102000_2015102200",
> "status": "NEW",
> ……….
> },
> {
> "uuid": "a8f6116f-acd6-46ac-be2f-021c2b291531",
> "name": "2015102100_2015102200",
> "status": "READY",
> ……….
> }
> ],
> "last_modified": 1448258568340,
> "descriptor": "v5",
> "create_time_utc": 1448244454401,
> "auto_merge_time_ranges": null,
> "retention_range": 0,
> "size_kb": 0,
> "input_records_count": 0,
> "input_records_size": 0
> },
> {
> "uuid": "c0dc404a-cfe6-4315-ac1c-ef52b27f8335",
> "name": "v5_21",
> "owner": "ADMIN",
> "version": null,
> "cost": 50,
> "status": "READY",
> "segments": [
> {
> "uuid": "c8e195ba-51a9-4fd9-be86-40e9943bcb1c",
> "name": "2015102100_2015102200",
>"status": "READY",
> ……….
> }
> ],
> "last_modified": 1448257690944,
> "descriptor": "v5_21",
> "create_time_utc": 1448247295576,
> "auto_merge_time_ranges": null,
> "retention_range": 0,
> "size_kb": 0,
> "input_records_count": 0,
> "input_records_size": 0
> }
> ]
> I don’t understand why this happen. The v5_21 cube and v5 cube base a sample
> fact table and project.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (KYLIN-1161) Rest API /api/cubes?cubeName= is doing fuzzy match instead of exact match
[
https://issues.apache.org/jira/browse/KYLIN-1161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15057200#comment-15057200
]
Shaofeng SHI commented on KYLIN-1161:
-
Jason, could you please update this URL to the real working one? I'm afraid it
would confuse user, thanks;
> Rest API /api/cubes?cubeName= is doing fuzzy match instead of exact match
> --
>
> Key: KYLIN-1161
> URL: https://issues.apache.org/jira/browse/KYLIN-1161
> Project: Kylin
> Issue Type: Improvement
> Components: REST Service
>Affects Versions: v1.1, v1.0, v0.7.2, v0.7.1, v1.1.1
>Reporter: Shaofeng SHI
>Assignee: Zhong,Jason
> Labels: QE
> Fix For: v1.2, 2.0
>
>
> This is reported by Yang HaiLe from dev mailing list:
> When I use restful api to get details of a cube, I found that the server
> will return more than one cube’s detail I want. For example:
> I use the url:
> http://server_ip:7070/kylin/api/cubes?cubeName=v5&limit=15&offset=0. The
> server will return these:
>[
> {
> "uuid": "876dd9d8-bc40-45fd-be6b-e0429ff9d4d1",
> "name": "v5",
> "owner": "ADMIN",
> "version": null,
> "cost": 50,
> "status": "READY",
> "segments": [
> {
> "uuid": "dd80cab3-1069-4333-8463-e0e48f2602c6",
> "name": "2015102000_2015102100",
> "status": "READY",
> ……….
> },
> {
> "uuid": "960e44b8-ac38-4483-8dbe-6a6a817ff4e1",
> "name": "2015102000_2015102200",
> "status": "NEW",
> ……….
> },
> {
> "uuid": "a8f6116f-acd6-46ac-be2f-021c2b291531",
> "name": "2015102100_2015102200",
> "status": "READY",
> ……….
> }
> ],
> "last_modified": 1448258568340,
> "descriptor": "v5",
> "create_time_utc": 1448244454401,
> "auto_merge_time_ranges": null,
> "retention_range": 0,
> "size_kb": 0,
> "input_records_count": 0,
> "input_records_size": 0
> },
> {
> "uuid": "c0dc404a-cfe6-4315-ac1c-ef52b27f8335",
> "name": "v5_21",
> "owner": "ADMIN",
> "version": null,
> "cost": 50,
> "status": "READY",
> "segments": [
> {
> "uuid": "c8e195ba-51a9-4fd9-be86-40e9943bcb1c",
> "name": "2015102100_2015102200",
>"status": "READY",
> ……….
> }
> ],
> "last_modified": 1448257690944,
> "descriptor": "v5_21",
> "create_time_utc": 1448247295576,
> "auto_merge_time_ranges": null,
> "retention_range": 0,
> "size_kb": 0,
> "input_records_count": 0,
> "input_records_size": 0
> }
> ]
> I don’t understand why this happen. The v5_21 cube and v5 cube base a sample
> fact table and project.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KYLIN-1157) CubeMigrationCLI doesn't copy ACL
[ https://issues.apache.org/jira/browse/KYLIN-1157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaofeng SHI updated KYLIN-1157: Issue Type: Improvement (was: Bug) Although the "copy cube ACL" has been implemented in CubeMigrationCLI, while it has fallback, which I don't suggest to use untill this issue is fixed: KYLIN-1230 > CubeMigrationCLI doesn't copy ACL > - > > Key: KYLIN-1157 > URL: https://issues.apache.org/jira/browse/KYLIN-1157 > Project: Kylin > Issue Type: Improvement >Affects Versions: v1.1 >Reporter: Shaofeng SHI >Assignee: Shaofeng SHI > Fix For: v2.0, v1.2 > > > CubeMigrationCLI will copy cube and related resources from one metadata store > to another, but the ACL wasn't copied. Today we need manually add the ACL > after cube migrated, this should be automated. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KYLIN-1154) Load job page is very slow when there are a lot of history job
[ https://issues.apache.org/jira/browse/KYLIN-1154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaofeng SHI updated KYLIN-1154: Issue Type: Improvement (was: Bug) > Load job page is very slow when there are a lot of history job > -- > > Key: KYLIN-1154 > URL: https://issues.apache.org/jira/browse/KYLIN-1154 > Project: Kylin > Issue Type: Improvement > Components: Job Engine, Metadata >Affects Versions: v1.1, v1.0, v1.1.1 >Reporter: Shaofeng SHI >Assignee: Shaofeng SHI > Fix For: v2.0, v1.2 > > > The key of a job is the job uuid, which doesn't have time information; To get > the latest job, Kylin need to scan full jobs and then parse the time from > value, which caused the bad performance. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KYLIN-1149) When yarn return an incomplete job tracking URL, Kylin will fail to get job status
[
https://issues.apache.org/jira/browse/KYLIN-1149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shaofeng SHI updated KYLIN-1149:
Issue Type: Improvement (was: Bug)
> When yarn return an incomplete job tracking URL, Kylin will fail to get job
> status
> --
>
> Key: KYLIN-1149
> URL: https://issues.apache.org/jira/browse/KYLIN-1149
> Project: Kylin
> Issue Type: Improvement
> Components: Job Engine
>Affects Versions: v1.1, v1.0, v0.7.2, v0.7.1, v1.1.1
>Reporter: Shaofeng SHI
>Assignee: Shaofeng SHI
> Fix For: v2.0, v1.2
>
>
> When yarn return an incomplete job tracking URL, Kylin will fail to get job
> status, then the cube job will be in "Error" state:
> {code}
> [pool-9-thread-8]:[2015-11-16
> 04:58:32,062][ERROR][org.apache.kylin.engine.mr.common.HadoopStatusChecker.checkStatus(HadoopStatusChecker.java:91)]
> - error check status
> java.lang.IllegalArgumentException: host parameter is null
> at
> org.apache.commons.httpclient.HttpConnection.setHost(HttpConnection.java:249)
> at
> org.apache.commons.httpclient.SimpleHttpConnectionManager.getConnectionWithTimeout(SimpleHttpConnectionManager.java:189)
> at
> org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:153)
> at
> org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:397)
> at
> org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:323)
> at
> org.apache.kylin.engine.mr.common.HadoopStatusGetter.getHttpResponse(HadoopStatusGetter.java:77)
> at
> org.apache.kylin.engine.mr.common.HadoopStatusGetter.get(HadoopStatusGetter.java:54)
> at
> org.apache.kylin.engine.mr.common.HadoopStatusChecker.checkStatus(HadoopStatusChecker.java:56)
> at
> org.apache.kylin.engine.mr.common.MapReduceExecutable.doWork(MapReduceExecutable.java:136)
> at
> org.apache.kylin.job.execution.AbstractExecutable.execute(AbstractExecutable.java:107)
> at
> org.apache.kylin.job.execution.DefaultChainedExecutable.doWork(DefaultChainedExecutable.java:50)
> at
> org.apache.kylin.job.execution.AbstractExecutable.execute(AbstractExecutable.java:107)
> at
> org.apache.kylin.job.impl.threadpool.DefaultScheduler$JobRunner.run(DefaultScheduler.java:124)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> Kylin should better check whether the URL is valid before visit it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KYLIN-1139) Hive job not starting due to error "conflicting lock present for default mode EXCLUSIVE "
[
https://issues.apache.org/jira/browse/KYLIN-1139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shaofeng SHI updated KYLIN-1139:
Issue Type: Improvement (was: Bug)
> Hive job not starting due to error "conflicting lock present for default mode
> EXCLUSIVE "
> -
>
> Key: KYLIN-1139
> URL: https://issues.apache.org/jira/browse/KYLIN-1139
> Project: Kylin
> Issue Type: Improvement
>Affects Versions: v1.1, v1.0
>Reporter: Shaofeng SHI
>Assignee: Shaofeng SHI
> Fix For: v2.0, v1.2
>
>
> some kylin hive jobs are not starting due to "conflicting lock present for
> default mode EXCLUSIVE ", the log in the first cube build step is similar to :
> {code}
> conflicting lock present for default mode EXCLUSIVE
> conflicting lock present for default mode EXCLUSIVE
> conflicting lock present for default mode EXCLUSIVE
> conflicting lock present for default mode EXCLUSIVE
> FAILED: Error in acquiring locks: Locks on the underlying objects cannot be
> acquired. retry after some time
> {code}
> This is related with Hive's concurrency model:
> https://cwiki.apache.org/confluence/display/Hive/Locking
> If the underlying table is locked by other users, Kylin will not be able to
> read from it. Hadoop admin suggest to set "hive.support.concurrency" as false
> and rerun the job.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KYLIN-1101) Allow "YYYYMMDD" as a date partition column
[ https://issues.apache.org/jira/browse/KYLIN-1101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaofeng SHI updated KYLIN-1101: Issue Type: Improvement (was: Bug) > Allow "MMDD" as a date partition column > --- > > Key: KYLIN-1101 > URL: https://issues.apache.org/jira/browse/KYLIN-1101 > Project: Kylin > Issue Type: Improvement >Affects Versions: 1.2, 2.0 >Reporter: liyang >Assignee: liyang > Fix For: v2.0, v1.2 > > Attachments: 1.x - > 0001-KYLIN-1101-Allow-MMDD-as-a-date-partition-column.patch, 2.x - > 0001-KYLIN-1101-Allow-MMDD-as-a-date-partition-column.patch > > > Many hive tables use the format "MMDD" as an effective date column. > However Kylin currently require the date format to be "-MM-DD". Support > "MMDD" right away will save user's effort in many cases. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KYLIN-1099) Support dictionary of cardinality over 10 millions
[ https://issues.apache.org/jira/browse/KYLIN-1099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaofeng SHI updated KYLIN-1099: Issue Type: Improvement (was: Bug) > Support dictionary of cardinality over 10 millions > -- > > Key: KYLIN-1099 > URL: https://issues.apache.org/jira/browse/KYLIN-1099 > Project: Kylin > Issue Type: Improvement > Components: Job Engine >Reporter: liyang >Assignee: liyang > Fix For: v2.0, v1.2 > > Attachments: 1.x - > 0001-KYLIN-1099-Support-dictionary-of-cardinality-over-10.patch, > 1.x-0001-KYLIN-1099-Remove-dedup-in-dictionary-value-enumerat.patch, > 2.x-0001-KYLIN-1099-Support-dictionary-of-cardinality-over-10.patch > > > Many use cases involve columns with high cardinality over 10 millions. > Dictionary should be supported on these columns assuming mem is sufficient. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KYLIN-1105) Cache in AbstractRowKeyEncoder.createInstance() is useless
[ https://issues.apache.org/jira/browse/KYLIN-1105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaofeng SHI updated KYLIN-1105: Issue Type: Improvement (was: Bug) > Cache in AbstractRowKeyEncoder.createInstance() is useless > -- > > Key: KYLIN-1105 > URL: https://issues.apache.org/jira/browse/KYLIN-1105 > Project: Kylin > Issue Type: Improvement >Reporter: liyang >Assignee: liyang > Fix For: v2.0, v1.2 > > > The current cache in AbstractRowKeyEncoder.createInstance() is not > implemented correctly. Put key being cube name and get key being segment > table name, the cache will never hit. > Also don't see a strong reason why the row key encoder needs a cache. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KYLIN-1095) Update AdminLTE to latest version
[ https://issues.apache.org/jira/browse/KYLIN-1095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaofeng SHI updated KYLIN-1095: Issue Type: Improvement (was: Bug) > Update AdminLTE to latest version > - > > Key: KYLIN-1095 > URL: https://issues.apache.org/jira/browse/KYLIN-1095 > Project: Kylin > Issue Type: Improvement > Components: Web >Affects Versions: v2.0, v1.1, v1.0 >Reporter: Luke Han >Assignee: Zhong,Jason > Fix For: v2.0, v1.2 > > > Update AdminLTE to latest version and update fonts dependency. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KYLIN-1058) Remove "right join" during model creation
[ https://issues.apache.org/jira/browse/KYLIN-1058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaofeng SHI updated KYLIN-1058: Issue Type: Improvement (was: Bug) > Remove "right join" during model creation > - > > Key: KYLIN-1058 > URL: https://issues.apache.org/jira/browse/KYLIN-1058 > Project: Kylin > Issue Type: Improvement >Reporter: liyang >Assignee: Zhong,Jason > Labels: QE > Fix For: v2.0, v1.2 > > > I don't think Kylin support "right join" (in addition to inner join and left > join). Remove it in model creation options. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KYLIN-1234) Cube ACL does not work
[ https://issues.apache.org/jira/browse/KYLIN-1234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15058118#comment-15058118 ] Shaofeng SHI commented on KYLIN-1234: - Could you set "kylin.query.security.enabled=true" in conf/kylin.properties, restart Kylin server and try again? This property wasn't appeared in the default config file, and its default value was "false" which means no security check. I think it need be changed to true by default. Thanks for the reporting! > Cube ACL does not work > -- > > Key: KYLIN-1234 > URL: https://issues.apache.org/jira/browse/KYLIN-1234 > Project: Kylin > Issue Type: Bug > Components: REST Service >Affects Versions: v1.1 >Reporter: Marek Wiewiorka >Assignee: Zhong,Jason > > Steps to reproduce the issue: > 1)Create a user in the LDAP not assigning it to any group > 2)User is not able to log in the Web UI - since it's not a member of any > default group, nor a member of admin group. > 3)User can however query any cube using REST api. > == > I would expect that unless a user or group has CUBE_QUERY priv granted it > should not be allowed to view the data. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KYLIN-1244) In query window, enable fast copy&paste by double clicking tables/columns' names.
[ https://issues.apache.org/jira/browse/KYLIN-1244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15067673#comment-15067673 ] Shaofeng SHI commented on KYLIN-1244: - This is the feature that I had expected to have; thank you Chunen! > In query window, enable fast copy&paste by double clicking tables/columns' > names. > - > > Key: KYLIN-1244 > URL: https://issues.apache.org/jira/browse/KYLIN-1244 > Project: Kylin > Issue Type: Improvement > Components: Web >Affects Versions: v2.0, v1.2, v1.1.1 >Reporter: nichunen >Assignee: Zhong,Jason > Fix For: v2.1, v1.3 > > Attachments: KYLIN-1244.patch > > > When do query in kylin on the web, it's not very convenient to copy&paste > tables/columns' names which are sometimes very long. > Attached is my patch to add a feature for fast copy&paste, double click a > table/column's name on the list, it will then be paste on the query window. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KYLIN-1241) support machine resource isolation in project level with different kylin_job_conf.xml file
[ https://issues.apache.org/jira/browse/KYLIN-1241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15067694#comment-15067694 ] Shaofeng SHI commented on KYLIN-1241: - Dong, I agree the idea that we need project level properties, that can solve many issues; While putting project specific config files in KYLIN_HOME/conf might be difficult to use, as it need admin to create and maintain those files each time. A better way is to provide an entry to let user to do this, like in Kylin UI; and these information should be persisted in Kylin metadata. Then each time there is a change, user can do that by himself. Furthermore, Kylin can allow cube level configurations. > support machine resource isolation in project level with different > kylin_job_conf.xml file > -- > > Key: KYLIN-1241 > URL: https://issues.apache.org/jira/browse/KYLIN-1241 > Project: Kylin > Issue Type: New Feature > Components: Job Engine >Affects Versions: v1.1.1 >Reporter: Wang,Dong >Assignee: ZhouQianhao >Priority: Minor > Fix For: v1.3 > > Attachments: KYLIN-1241.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KYLIN-1077) Support Hive View as Lookup Table
[ https://issues.apache.org/jira/browse/KYLIN-1077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15067753#comment-15067753 ] Shaofeng SHI commented on KYLIN-1077: - [~francescopalmiotto] are you working on this? is there any update? > Support Hive View as Lookup Table > - > > Key: KYLIN-1077 > URL: https://issues.apache.org/jira/browse/KYLIN-1077 > Project: Kylin > Issue Type: Improvement >Affects Versions: v1.1 >Reporter: Francesco Palmiotto >Assignee: Shaofeng SHI > > If we use a view as a lookup table the cube building job fails when executing > the 3rd step (Build Dimension Dictionary) with this log: > java.io.IOException: java.lang.NullPointerException > at > org.apache.kylin.dict.lookup.HiveTable.getSignature(HiveTable.java:72) > at > org.apache.kylin.dict.DictionaryManager.buildDictionary(DictionaryManager.java:202) > at > org.apache.kylin.cube.CubeManager.buildDictionary(CubeManager.java:166) > at > org.apache.kylin.cube.cli.DictionaryGeneratorCLI.processSegment(DictionaryGeneratorCLI.java:52) > at > org.apache.kylin.cube.cli.DictionaryGeneratorCLI.processSegment(DictionaryGeneratorCLI.java:41) > at > org.apache.kylin.job.hadoop.dict.CreateDictionaryJob.run(CreateDictionaryJob.java:52) > at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:70) > at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:84) > at > org.apache.kylin.job.common.HadoopShellExecutable.doWork(HadoopShellExecutable.java:62) > at > org.apache.kylin.job.execution.AbstractExecutable.execute(AbstractExecutable.java:107) > at > org.apache.kylin.job.execution.DefaultChainedExecutable.doWork(DefaultChainedExecutable.java:51) > at > org.apache.kylin.job.execution.AbstractExecutable.execute(AbstractExecutable.java:107) > at > org.apache.kylin.job.impl.threadpool.DefaultScheduler$JobRunner.run(DefaultScheduler.java:130) > 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.NullPointerException > result code:2 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KYLIN-1242) support building the back end and the front end seperately
[ https://issues.apache.org/jira/browse/KYLIN-1242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15067785#comment-15067785 ] Shaofeng SHI commented on KYLIN-1242: - To build the Kylin binary package with proxy, you need set http proxy for both bower and npm: export http_proxy=http://proxy-host:port npm config set proxy http://proxy-host:port after that, you should be able to build with "./script/package.sh" Just FYI if someone having problem with as-is method. > support building the back end and the front end seperately > -- > > Key: KYLIN-1242 > URL: https://issues.apache.org/jira/browse/KYLIN-1242 > Project: Kylin > Issue Type: Improvement > Components: General >Affects Versions: v1.1.1 >Reporter: Wang,Dong >Assignee: hongbin ma >Priority: Minor > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (KYLIN-1216) Can't parse DateFormat like 'YYYYMMDD' correctly in query
[
https://issues.apache.org/jira/browse/KYLIN-1216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shaofeng SHI closed KYLIN-1216.
---
Resolved in release 1.2
> Can't parse DateFormat like 'MMDD' correctly in query
> -
>
> Key: KYLIN-1216
> URL: https://issues.apache.org/jira/browse/KYLIN-1216
> Project: Kylin
> Issue Type: Bug
> Components: Query Engine
>Affects Versions: 1.2, 2.0
>Reporter: Yerui Sun
>Assignee: Yerui Sun
> Fix For: v2.0, v1.2
>
> Attachments: KYLIN-1216-1.x-staging.patch,
> KYLIN-1216-2.x-staging.patch
>
>
> Kylin has support date format as 'MMDD' since KYLIN-1101, and could read
> data and build cube successfully with this format.
> However, the query sql contains " dt='20151208' " can't be parsed, the reason
> is HBaseKeyRange.initPartitionRange still using default format '-MM-DD'
> only, not read from partition desc.
> Here's the trace:
> {code}
> Caused by: java.lang.IllegalArgumentException: '20150901' is not a valid date
> of pattern '-MM-dd'
> at
> org.apache.kylin.common.util.DateFormat.stringToDate(DateFormat.java:78)
> at
> org.apache.kylin.common.util.DateFormat.stringToDate(DateFormat.java:70)
> at
> org.apache.kylin.storage.hbase.HBaseKeyRange.initPartitionRange(HBaseKeyRange.java:148)
> at
> org.apache.kylin.storage.hbase.HBaseKeyRange.init(HBaseKeyRange.java:127)
> at
> org.apache.kylin.storage.hbase.HBaseKeyRange.(HBaseKeyRange.java:101)
> at
> org.apache.kylin.storage.hbase.CubeStorageEngine.buildScanRanges(CubeStorageEngine.java:410)
> at
> org.apache.kylin.storage.hbase.CubeStorageEngine.search(CubeStorageEngine.java:134)
> at
> org.apache.kylin.query.enumerator.CubeEnumerator.queryStorage(CubeEnumerator.java:149)
> at
> org.apache.kylin.query.enumerator.CubeEnumerator.moveNext(CubeEnumerator.java:74)
> at Baz$1$1.moveNext(Unknown Source)
> at
> org.apache.calcite.linq4j.EnumerableDefaults.groupBy_(EnumerableDefaults.java:737)
> at
> org.apache.calcite.linq4j.EnumerableDefaults.groupBy(EnumerableDefaults.java:677)
> at
> org.apache.calcite.linq4j.DefaultEnumerable.groupBy(DefaultEnumerable.java:301)
> at Baz.bind(Unknown Source)
> at
> org.apache.calcite.jdbc.CalcitePrepare$CalciteSignature.enumerable(CalcitePrepare.java:281)
> at
> org.apache.calcite.jdbc.CalciteConnectionImpl.enumerable(CalciteConnectionImpl.java:235)
> at
> org.apache.calcite.jdbc.CalciteMetaImpl.createIterable(CalciteMetaImpl.java:533)
> at
> org.apache.calcite.avatica.AvaticaResultSet.execute(AvaticaResultSet.java:184)
> at
> org.apache.calcite.jdbc.CalciteResultSet.execute(CalciteResultSet.java:63)
> at
> org.apache.calcite.jdbc.CalciteResultSet.execute(CalciteResultSet.java:42)
> at
> org.apache.calcite.avatica.AvaticaConnection$1.execute(AvaticaConnection.java:473)
> at
> org.apache.calcite.jdbc.CalciteMetaImpl.prepareAndExecute(CalciteMetaImpl.java:566)
> at
> org.apache.calcite.avatica.AvaticaConnection.prepareAndExecuteInternal(AvaticaConnection.java:477)
> at
> org.apache.calcite.avatica.AvaticaStatement.executeInternal(AvaticaStatement.java:109)
> ... 83 more
> Caused by: java.text.ParseException: Unparseable date: "20150901"
> at java.text.DateFormat.parse(DateFormat.java:366)
> at
> org.apache.kylin.common.util.DateFormat.stringToDate(DateFormat.java:76)
> ... 106 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KYLIN-1152) ResourceStore should read content and timestamp in one go
[ https://issues.apache.org/jira/browse/KYLIN-1152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaofeng SHI updated KYLIN-1152: Assignee: liyang > ResourceStore should read content and timestamp in one go > - > > Key: KYLIN-1152 > URL: https://issues.apache.org/jira/browse/KYLIN-1152 > Project: Kylin > Issue Type: Bug >Reporter: liyang >Assignee: liyang > Fix For: v2.0, v1.2 > > > ResourceStore should read content and timestamp in one go. Otherwise scenario > below might happen: > - A read content > - B write content & timestamp > - A read timestamp > - A write again which overwrite B without detection -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (KYLIN-1083) unable to build sample cube in HDP 2.3, HBASE 1.x
[ https://issues.apache.org/jira/browse/KYLIN-1083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaofeng SHI resolved KYLIN-1083. - Resolution: Not A Problem > unable to build sample cube in HDP 2.3, HBASE 1.x > - > > Key: KYLIN-1083 > URL: https://issues.apache.org/jira/browse/KYLIN-1083 > Project: Kylin > Issue Type: Bug > Components: General >Affects Versions: 1.x-HBase1.1.3 > Environment: HDP 2.3 > KYLIN 1.x-HBase1.x SHA:19976c137d079e1bcfaa9b2fec6c9698f2c1b7ca >Reporter: gil michlin >Assignee: Shaofeng SHI > > based on KYLIN-892 I was able to login and create a sample cube > however every time I am trying to run the build cube I am failing on > #14 Step Name: Convert Cuboid Data to HFile > -conf /opt/kylin/conf/kylin_job_conf.xml -cubename kylin_sales_cube -input > /kylin/kylin_metadata/kylin-dd85844a-f1ba-49ed-8dc6-bb0aa5766ecb/kylin_sales_cube/cuboid/* > -output > hdfs://sandbox.hortonworks.com:8020/kylin/kylin_metadata/kylin-dd85844a-f1ba-49ed-8dc6-bb0aa5766ecb/kylin_sales_cube/hfile > -htablename KYLIN_K7PEXRD5EV -jobname > Kylin_HFile_Generator_kylin_sales_cube_Step > java.lang.IllegalArgumentException: Can not create a Path from a null string > at org.apache.hadoop.fs.Path.checkPathArg(Path.java:122) > at org.apache.hadoop.fs.Path.(Path.java:134) > at org.apache.hadoop.fs.Path.(Path.java:88) > at > org.apache.hadoop.hbase.mapreduce.HFileOutputFormat2.configurePartitioner(HFileOutputFormat2.java:591) > at > org.apache.hadoop.hbase.mapreduce.HFileOutputFormat2.configureIncrementalLoad(HFileOutputFormat2.java:440) > at > org.apache.hadoop.hbase.mapreduce.HFileOutputFormat2.configureIncrementalLoad(HFileOutputFormat2.java:405) > at > org.apache.hadoop.hbase.mapreduce.HFileOutputFormat.configureIncrementalLoad(HFileOutputFormat.java:91) > at > org.apache.kylin.job.hadoop.cube.CubeHFileJob.run(CubeHFileJob.java:86) > at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:70) > at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:84) > at > org.apache.kylin.job.common.MapReduceExecutable.doWork(MapReduceExecutable.java:113) > at > org.apache.kylin.job.execution.AbstractExecutable.execute(AbstractExecutable.java:107) > at > org.apache.kylin.job.execution.DefaultChainedExecutable.doWork(DefaultChainedExecutable.java:51) > at > org.apache.kylin.job.execution.AbstractExecutable.execute(AbstractExecutable.java:107) > at > org.apache.kylin.job.impl.threadpool.DefaultScheduler$JobRunner.run(DefaultScheduler.java:130) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:745) > result code:2 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (KYLIN-1083) unable to build sample cube in HDP 2.3, HBASE 1.x
[ https://issues.apache.org/jira/browse/KYLIN-1083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaofeng SHI closed KYLIN-1083. --- Close this JIRA as this is an hbase env issue. > unable to build sample cube in HDP 2.3, HBASE 1.x > - > > Key: KYLIN-1083 > URL: https://issues.apache.org/jira/browse/KYLIN-1083 > Project: Kylin > Issue Type: Bug > Components: General >Affects Versions: 1.x-HBase1.1.3 > Environment: HDP 2.3 > KYLIN 1.x-HBase1.x SHA:19976c137d079e1bcfaa9b2fec6c9698f2c1b7ca >Reporter: gil michlin >Assignee: Shaofeng SHI > > based on KYLIN-892 I was able to login and create a sample cube > however every time I am trying to run the build cube I am failing on > #14 Step Name: Convert Cuboid Data to HFile > -conf /opt/kylin/conf/kylin_job_conf.xml -cubename kylin_sales_cube -input > /kylin/kylin_metadata/kylin-dd85844a-f1ba-49ed-8dc6-bb0aa5766ecb/kylin_sales_cube/cuboid/* > -output > hdfs://sandbox.hortonworks.com:8020/kylin/kylin_metadata/kylin-dd85844a-f1ba-49ed-8dc6-bb0aa5766ecb/kylin_sales_cube/hfile > -htablename KYLIN_K7PEXRD5EV -jobname > Kylin_HFile_Generator_kylin_sales_cube_Step > java.lang.IllegalArgumentException: Can not create a Path from a null string > at org.apache.hadoop.fs.Path.checkPathArg(Path.java:122) > at org.apache.hadoop.fs.Path.(Path.java:134) > at org.apache.hadoop.fs.Path.(Path.java:88) > at > org.apache.hadoop.hbase.mapreduce.HFileOutputFormat2.configurePartitioner(HFileOutputFormat2.java:591) > at > org.apache.hadoop.hbase.mapreduce.HFileOutputFormat2.configureIncrementalLoad(HFileOutputFormat2.java:440) > at > org.apache.hadoop.hbase.mapreduce.HFileOutputFormat2.configureIncrementalLoad(HFileOutputFormat2.java:405) > at > org.apache.hadoop.hbase.mapreduce.HFileOutputFormat.configureIncrementalLoad(HFileOutputFormat.java:91) > at > org.apache.kylin.job.hadoop.cube.CubeHFileJob.run(CubeHFileJob.java:86) > at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:70) > at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:84) > at > org.apache.kylin.job.common.MapReduceExecutable.doWork(MapReduceExecutable.java:113) > at > org.apache.kylin.job.execution.AbstractExecutable.execute(AbstractExecutable.java:107) > at > org.apache.kylin.job.execution.DefaultChainedExecutable.doWork(DefaultChainedExecutable.java:51) > at > org.apache.kylin.job.execution.AbstractExecutable.execute(AbstractExecutable.java:107) > at > org.apache.kylin.job.impl.threadpool.DefaultScheduler$JobRunner.run(DefaultScheduler.java:130) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:745) > result code:2 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KYLIN-1241) support machine resource isolation in project level with different kylin_job_conf.xml file
[ https://issues.apache.org/jira/browse/KYLIN-1241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15069103#comment-15069103 ] Shaofeng SHI commented on KYLIN-1241: - Dong, I can understand, this is a good solution and can solve your pain quickly. While from Kylin's perspective, we hope to provide the flexibility and keep the usability: it should be easy to use for both user and kylin admin. So I'm wondering if there is a better way to solve this. Dividing the job configs by cube capacity into small, medium and large ones was a historic decision. From my experience it is not very useful; each project may have both small and large cubes, they have to share the same properties, this is not flexible. So, maybe we can allow user to upload a job conf file per project/cube, which is in the same format as kylin_job_conf.xml. The content will be persisted into metadata store, and user can upload/delete it from Kylin UI. When building a cube, Kylin will seek whether there is a cube specific conf file; if yes will use it; Otherwise will seek the project specific one; Finally if both cube and project don't have, will use the one that provided by admin in KYLIN_HOME/conf/. > support machine resource isolation in project level with different > kylin_job_conf.xml file > -- > > Key: KYLIN-1241 > URL: https://issues.apache.org/jira/browse/KYLIN-1241 > Project: Kylin > Issue Type: New Feature > Components: Job Engine >Affects Versions: v1.1.1 >Reporter: Wang,Dong >Assignee: ZhouQianhao >Priority: Minor > Fix For: v1.3 > > Attachments: KYLIN-1241.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KYLIN-1241) support machine resource isolation in project level with different kylin_job_conf.xml file
[ https://issues.apache.org/jira/browse/KYLIN-1241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15069109#comment-15069109 ] Shaofeng SHI commented on KYLIN-1241: - yes, we should allow user to config/owerwrite all possible configs, not just the queue name; > support machine resource isolation in project level with different > kylin_job_conf.xml file > -- > > Key: KYLIN-1241 > URL: https://issues.apache.org/jira/browse/KYLIN-1241 > Project: Kylin > Issue Type: New Feature > Components: Job Engine >Affects Versions: v1.1.1 >Reporter: Wang,Dong >Assignee: ZhouQianhao >Priority: Minor > Fix For: v1.3 > > Attachments: KYLIN-1241.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KYLIN-1243) Can't get dictionary value for column
[ https://issues.apache.org/jira/browse/KYLIN-1243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15069115#comment-15069115 ] Shaofeng SHI commented on KYLIN-1243: - Could you upgrade to a newer version like v1.1 or v1.2 to see whether it still there? 0.7.2 was released in 5 monthes ago, during this period there are many bug fixes and enhancements, your issue might have already been fixed. > Can't get dictionary value for column > - > > Key: KYLIN-1243 > URL: https://issues.apache.org/jira/browse/KYLIN-1243 > Project: Kylin > Issue Type: Bug > Components: Query Engine >Affects Versions: v0.7.2 >Reporter: Abhilash L L >Assignee: liyang > > Hello for one of the dimensions it started giving the following error and the > response was empty. > [http-bio-7071-exec-11]:[2015-12-17 > 13:48:23,548][ERROR][org.apache.kylin.cube.kv.RowKeyColumnIO.readColumnString(RowKeyColumnIO.java:113)] > - Can't get dictionary value for column DIM_FKEY (id = 23561) > After going through the RowKeyColumnIO code a bit.. Seems like the in memory > lookup table is 'corrupt' ? > After restarting, it started working fine. > We are on 0.72 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KYLIN-458) OAuth Support for user login
[ https://issues.apache.org/jira/browse/KYLIN-458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15069355#comment-15069355 ] Shaofeng SHI commented on KYLIN-458: Is Oauth selected for SSO? I'm doing SSO with SAML (https://issues.apache.org/jira/browse/KYLIN-1219), not sure whether they can co-exist in Kylin, and whether Oauth is a valid case . > OAuth Support for user login > > > Key: KYLIN-458 > URL: https://issues.apache.org/jira/browse/KYLIN-458 > Project: Kylin > Issue Type: Wish > Components: REST Service, Web >Reporter: Luke Han > Labels: github-import > Fix For: Backlog > > Attachments: 0001-Kylin-458-initial.patch > > > Support login with OAuth protocol > Imported from GitHub > Url: https://github.com/KylinOLAP/Kylin/issues/47 > Created by: [lukehan|https://github.com/lukehan] > Labels: newfeature, > Created at: Sat Nov 08 20:39:52 CST 2014 > State: open -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KYLIN-1243) Can't get dictionary value for column
[ https://issues.apache.org/jira/browse/KYLIN-1243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15069360#comment-15069360 ] Shaofeng SHI commented on KYLIN-1243: - I didn't see this error before; If it can be reproduced, should be easy to track. > Can't get dictionary value for column > - > > Key: KYLIN-1243 > URL: https://issues.apache.org/jira/browse/KYLIN-1243 > Project: Kylin > Issue Type: Bug > Components: Query Engine >Affects Versions: v0.7.2 >Reporter: Abhilash L L >Assignee: liyang > > Hello for one of the dimensions it started giving the following error and the > response was empty. > [http-bio-7071-exec-11]:[2015-12-17 > 13:48:23,548][ERROR][org.apache.kylin.cube.kv.RowKeyColumnIO.readColumnString(RowKeyColumnIO.java:113)] > - Can't get dictionary value for column DIM_FKEY (id = 23561) > After going through the RowKeyColumnIO code a bit.. Seems like the in memory > lookup table is 'corrupt' ? > After restarting, it started working fine. > We are on 0.72 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KYLIN-458) OAuth Support for user login
[ https://issues.apache.org/jira/browse/KYLIN-458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15069712#comment-15069712 ] Shaofeng SHI commented on KYLIN-458: Thanks Vipin for the comment; Your trial is very good; While I think SAML is a more common standard in terms of human SSO than OAuth (as you mentioned, OAuth is mainly for one system to access data in another system on behalf of the user); One case is our corporate's SSO/2FA solution supports SAML but no OAuth; So far we haven't saw a scenario to use OAuth in Kylin; Based on above, I would release the SAML support, and hold the OAuth until there is a real case for it (the user can apply this patch and did a verification), or Luke may provide some background information about this requirement. Just let me know your comment, thanks! > OAuth Support for user login > > > Key: KYLIN-458 > URL: https://issues.apache.org/jira/browse/KYLIN-458 > Project: Kylin > Issue Type: Wish > Components: REST Service, Web >Reporter: Luke Han > Labels: github-import > Fix For: Backlog > > Attachments: 0001-Kylin-458-initial.patch > > > Support login with OAuth protocol > Imported from GitHub > Url: https://github.com/KylinOLAP/Kylin/issues/47 > Created by: [lukehan|https://github.com/lukehan] > Labels: newfeature, > Created at: Sat Nov 08 20:39:52 CST 2014 > State: open -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (KYLIN-1250) Got NPE when discarding a job
Shaofeng SHI created KYLIN-1250:
---
Summary: Got NPE when discarding a job
Key: KYLIN-1250
URL: https://issues.apache.org/jira/browse/KYLIN-1250
Project: Kylin
Issue Type: Bug
Components: General
Affects Versions: v1.2
Reporter: Shaofeng SHI
Assignee: Shaofeng SHI
Fix For: v1.3
User reported that he couldn't rebuild a cube, Kylin reports "The cube
has running job () please discard it and try again."
Then he tried to discard the job, but got an NullPointerException;
{code}
Caused by: java.lang.NullPointerException
at org.apache.kylin.rest.service.JobService.cancelJob(JobService.java:321)
at
org.apache.kylin.rest.service.JobService$$FastClassByCGLIB$$83a44b2a.invoke()
at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204)
at
org.springframework.aop.framework.Cglib2AopProxy$CglibMethodInvocation.invokeJoinpoint(Cglib2AopProxy.java:689)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
at
org.springframework.security.access.intercept.aopalliance.MethodSecurityInterceptor.invoke(MethodSecurityInterceptor.java:64)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInv
{code}
User said "We haven’t done the purge action. It’s possible that the bug was
triggered when we have made the changes to filtering while the cube was still
in the build process?"
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (KYLIN-1250) Got NPE when discarding a job
[
https://issues.apache.org/jira/browse/KYLIN-1250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15070528#comment-15070528
]
Shaofeng SHI commented on KYLIN-1250:
-
When user got an error in the first cube build job, he modified the cube
definition, at that moment Kylin dropped the building segment from metadata,
then the error job became an orphan (its linked segment doesn't exist); Then
when user wants to discard that job, the NPE was thrown.
The fix includes: 1) when drop segment, also discard the related job; 2) When
discard a job, if the segment doesn't exist, still allow it to proceed.
> Got NPE when discarding a job
> -
>
> Key: KYLIN-1250
> URL: https://issues.apache.org/jira/browse/KYLIN-1250
> Project: Kylin
> Issue Type: Bug
> Components: General
>Affects Versions: v1.2
>Reporter: Shaofeng SHI
>Assignee: Shaofeng SHI
> Fix For: v1.3
>
>
> User reported that he couldn't rebuild a cube, Kylin reports "The cube
> has running job () please discard it and try again."
> Then he tried to discard the job, but got an NullPointerException;
> {code}
> Caused by: java.lang.NullPointerException
> at org.apache.kylin.rest.service.JobService.cancelJob(JobService.java:321)
> at
> org.apache.kylin.rest.service.JobService$$FastClassByCGLIB$$83a44b2a.invoke()
> at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204)
> at
> org.springframework.aop.framework.Cglib2AopProxy$CglibMethodInvocation.invokeJoinpoint(Cglib2AopProxy.java:689)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
> at
> org.springframework.security.access.intercept.aopalliance.MethodSecurityInterceptor.invoke(MethodSecurityInterceptor.java:64)
> at
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInv
> {code}
> User said "We haven’t done the purge action. It’s possible that the bug was
> triggered when we have made the changes to filtering while the cube was still
> in the build process?"
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (KYLIN-1196) Prepare release v1.2
[ https://issues.apache.org/jira/browse/KYLIN-1196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaofeng SHI resolved KYLIN-1196. - Resolution: Done > Prepare release v1.2 > > > Key: KYLIN-1196 > URL: https://issues.apache.org/jira/browse/KYLIN-1196 > Project: Kylin > Issue Type: Task > Components: General >Reporter: Shaofeng SHI >Assignee: Shaofeng SHI > Fix For: v1.2 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
