[jira] [Created] (KYLIN-3175) Streaming segment lost TSRange after merge
Wang Cheng created KYLIN-3175: - Summary: Streaming segment lost TSRange after merge Key: KYLIN-3175 URL: https://issues.apache.org/jira/browse/KYLIN-3175 Project: Kylin Issue Type: Bug Reporter: Wang Cheng After merging streaming cube's segments, the final merged segment's TSRange is set to null and won't be updated, which causes it's start time/end time to be ZERO(1970-01-01). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KYLIN-3174) Scheduler should separate init and start
[ https://issues.apache.org/jira/browse/KYLIN-3174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16328354#comment-16328354 ] jiatao.tao commented on KYLIN-3174: --- Nowadays, Scheduler start when initing. These are two different life cycle and coupling is too tight > Scheduler should separate init and start > > > Key: KYLIN-3174 > URL: https://issues.apache.org/jira/browse/KYLIN-3174 > Project: Kylin > Issue Type: Improvement >Reporter: jiatao.tao >Assignee: jiatao.tao >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (KYLIN-3174) Scheduler should separate init and start
jiatao.tao created KYLIN-3174: - Summary: Scheduler should separate init and start Key: KYLIN-3174 URL: https://issues.apache.org/jira/browse/KYLIN-3174 Project: Kylin Issue Type: Bug Reporter: jiatao.tao -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (KYLIN-3174) Scheduler should separate init and start
[ https://issues.apache.org/jira/browse/KYLIN-3174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jiatao.tao updated KYLIN-3174: -- Issue Type: Improvement (was: Bug) > Scheduler should separate init and start > > > Key: KYLIN-3174 > URL: https://issues.apache.org/jira/browse/KYLIN-3174 > Project: Kylin > Issue Type: Improvement >Reporter: jiatao.tao >Assignee: jiatao.tao >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (KYLIN-3174) Scheduler should separate init and start
[ https://issues.apache.org/jira/browse/KYLIN-3174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jiatao.tao reassigned KYLIN-3174: - Assignee: jiatao.tao > Scheduler should separate init and start > > > Key: KYLIN-3174 > URL: https://issues.apache.org/jira/browse/KYLIN-3174 > Project: Kylin > Issue Type: Bug >Reporter: jiatao.tao >Assignee: jiatao.tao >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (KYLIN-3173) DefaultScheduler shutdown didn't reset field initialized.
[ https://issues.apache.org/jira/browse/KYLIN-3173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jiatao.tao reassigned KYLIN-3173: - Assignee: jiatao.tao > DefaultScheduler shutdown didn't reset field initialized. > - > > Key: KYLIN-3173 > URL: https://issues.apache.org/jira/browse/KYLIN-3173 > Project: Kylin > Issue Type: Bug >Reporter: jiatao.tao >Assignee: jiatao.tao >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KYLIN-3110) The dashboard page has some display problems.
[ https://issues.apache.org/jira/browse/KYLIN-3110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16328335#comment-16328335 ] peng.jianhua commented on KYLIN-3110: - Hi [~Zhixiong Chen], thanks very much! > The dashboard page has some display problems. > - > > Key: KYLIN-3110 > URL: https://issues.apache.org/jira/browse/KYLIN-3110 > Project: Kylin > Issue Type: Bug > Components: Web >Affects Versions: v2.3.0 >Reporter: peng.jianhua >Assignee: peng.jianhua >Priority: Major > Labels: patch > Fix For: v2.3.0 > > Attachments: > 0001-KYLIN-3110-The-dashboard-page-has-some-display-probl.patch, > incomplete_display_and_message_not_right.png > > > The dashboard page has some display problems. > 1. The 'Monthly' and 'Weekly' display incompletely; > 2. The 'showValue' should be 'Show Value'. > refer to [^incomplete_display_and_message_not_right.png] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (KYLIN-3173) DefaultScheduler shutdown didn't reset field initialized.
jiatao.tao created KYLIN-3173: - Summary: DefaultScheduler shutdown didn't reset field initialized. Key: KYLIN-3173 URL: https://issues.apache.org/jira/browse/KYLIN-3173 Project: Kylin Issue Type: Bug Reporter: jiatao.tao -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (KYLIN-3172) No such file or directory error with CreateLookupHiveViewMaterializationStep
[ https://issues.apache.org/jira/browse/KYLIN-3172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yiming.xu updated KYLIN-3172: - Summary: No such file or directory error with CreateLookupHiveViewMaterializationStep (was: No such file or directory error in build cube CreateLookupHiveViewMaterializationStep ) > No such file or directory error with CreateLookupHiveViewMaterializationStep > - > > Key: KYLIN-3172 > URL: https://issues.apache.org/jira/browse/KYLIN-3172 > Project: Kylin > Issue Type: Bug > Components: Job Engine >Affects Versions: v2.2.0 >Reporter: yiming.xu >Assignee: yiming.xu >Priority: Blocker > > No such file or directory error for CreateLookupHiveViewMaterializationStep > with kylin cluster mode > error describe: > ../tomcat/temp/beeline_6287823046370163072.hql (No such file or directory) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (KYLIN-3172) No such file or directory error in build cube CreateLookupHiveViewMaterializationStep
yiming.xu created KYLIN-3172: Summary: No such file or directory error in build cube CreateLookupHiveViewMaterializationStep Key: KYLIN-3172 URL: https://issues.apache.org/jira/browse/KYLIN-3172 Project: Kylin Issue Type: Bug Components: Job Engine Affects Versions: v2.2.0 Reporter: yiming.xu Assignee: Shaofeng SHI No such file or directory error for CreateLookupHiveViewMaterializationStep with kylin cluster mode error describe: ../tomcat/temp/beeline_6287823046370163072.hql (No such file or directory) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (KYLIN-3172) No such file or directory error in build cube CreateLookupHiveViewMaterializationStep
[ https://issues.apache.org/jira/browse/KYLIN-3172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yiming.xu reassigned KYLIN-3172: Assignee: yiming.xu (was: Shaofeng SHI) > No such file or directory error in build cube > CreateLookupHiveViewMaterializationStep > -- > > Key: KYLIN-3172 > URL: https://issues.apache.org/jira/browse/KYLIN-3172 > Project: Kylin > Issue Type: Bug > Components: Job Engine >Affects Versions: v2.2.0 >Reporter: yiming.xu >Assignee: yiming.xu >Priority: Blocker > > No such file or directory error for CreateLookupHiveViewMaterializationStep > with kylin cluster mode > error describe: > ../tomcat/temp/beeline_6287823046370163072.hql (No such file or directory) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KYLIN-3168) CubeHFileJob should use currentHBaseConfiguration but not new create hbase configuration
[ https://issues.apache.org/jira/browse/KYLIN-3168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16328259#comment-16328259 ] wuyingjun commented on KYLIN-3168: -- [~yimingliu] Please help me validating this bug and check the patch. > CubeHFileJob should use currentHBaseConfiguration but not new create hbase > configuration > > > Key: KYLIN-3168 > URL: https://issues.apache.org/jira/browse/KYLIN-3168 > Project: Kylin > Issue Type: Bug >Affects Versions: v2.2.0 >Reporter: wuyingjun >Assignee: wuyingjun >Priority: Major > Attachments: AfterModified.png, CubeHFileJob_Exception.png, > KYLIN-3168.patch > > > CubeHFileJob use new hbase configuration is not correct because when the > zookeeper quorum is not localhost (job worker)， kylin may account zookeeper > ConnectionLossException. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (KYLIN-3168) CubeHFileJob should use currentHBaseConfiguration but not new create hbase configuration
[ https://issues.apache.org/jira/browse/KYLIN-3168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wuyingjun updated KYLIN-3168: - Attachment: KYLIN-3168.patch AfterModified.png > CubeHFileJob should use currentHBaseConfiguration but not new create hbase > configuration > > > Key: KYLIN-3168 > URL: https://issues.apache.org/jira/browse/KYLIN-3168 > Project: Kylin > Issue Type: Bug >Affects Versions: v2.2.0 >Reporter: wuyingjun >Assignee: wuyingjun >Priority: Major > Attachments: AfterModified.png, CubeHFileJob_Exception.png, > KYLIN-3168.patch > > > CubeHFileJob use new hbase configuration is not correct because when the > zookeeper quorum is not localhost (job worker)， kylin may account zookeeper > ConnectionLossException. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KYLIN-3168) CubeHFileJob should use currentHBaseConfiguration but not new create hbase configuration
[ https://issues.apache.org/jira/browse/KYLIN-3168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16328254#comment-16328254 ] wuyingjun commented on KYLIN-3168: -- !AfterModified.png! [^KYLIN-3168.patch] > CubeHFileJob should use currentHBaseConfiguration but not new create hbase > configuration > > > Key: KYLIN-3168 > URL: https://issues.apache.org/jira/browse/KYLIN-3168 > Project: Kylin > Issue Type: Bug >Affects Versions: v2.2.0 >Reporter: wuyingjun >Assignee: wuyingjun >Priority: Major > Attachments: AfterModified.png, CubeHFileJob_Exception.png, > KYLIN-3168.patch > > > CubeHFileJob use new hbase configuration is not correct because when the > zookeeper quorum is not localhost (job worker)， kylin may account zookeeper > ConnectionLossException. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (KYLIN-3171) Support hadoop 3 release
Ted Yu created KYLIN-3171:
-
Summary: Support hadoop 3 release
Key: KYLIN-3171
URL: https://issues.apache.org/jira/browse/KYLIN-3171
Project: Kylin
Issue Type: Improvement
Reporter: Ted Yu
When compiling against hadoop 3, I got:
{code}
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:3.5.1:compile (default-compile)
on project kylin-engine-mr: Compilation failure: Compilation failure:
[ERROR]
/a/kylin/engine-mr/src/main/java/org/apache/kylin/engine/mr/common/DefaultSslProtocolSocketFactory.java:[29,36]
error: package org.apache.commons.httpclient does not exist
[ERROR]
/a/kylin/engine-mr/src/main/java/org/apache/kylin/engine/mr/common/DefaultSslProtocolSocketFactory.java:[30,36]
error: package org.apache.commons.httpclient does not exist
[ERROR]
/a/kylin/engine-mr/src/main/java/org/apache/kylin/engine/mr/common/DefaultSslProtocolSocketFactory.java:[31,43]
error: package org.apache.commons.httpclient.params does not exist
[ERROR]
/a/kylin/engine-mr/src/main/java/org/apache/kylin/engine/mr/common/DefaultSslProtocolSocketFactory.java:[32,45]
error: package org.apache.commons.httpclient.protocol does not exist
[ERROR]
/a/kylin/engine-mr/src/main/java/org/apache/kylin/engine/mr/common/DefaultSslProtocolSocketFactory.java:[33,45]
error: package org.apache.commons.httpclient.protocol does not exist
[ERROR]
/a/kylin/engine-mr/src/main/java/org/apache/kylin/engine/mr/common/DefaultSslProtocolSocketFactory.java:[41,56]
error: cannot find symbol
[ERROR] symbol: class SecureProtocolSocketFactory
[ERROR]
/a/kylin/engine-mr/src/main/java/org/apache/kylin/engine/mr/common/DefaultSslProtocolSocketFactory.java:[94,125]
error: cannot find symbol
[ERROR] symbol: class HttpConnectionParams
[ERROR] location: class DefaultSslProtocolSocketFactory
[ERROR]
/a/kylin/engine-mr/src/main/java/org/apache/kylin/engine/mr/common/DefaultSslProtocolSocketFactory.java:[94,196]
error: cannot find symbol
[ERROR] symbol: class ConnectTimeoutException
[ERROR] location: class DefaultSslProtocolSocketFactory
[ERROR]
/a/kylin/engine-mr/src/main/java/org/apache/kylin/engine/mr/common/DefaultSslProtocolSocketFactory.java:[105,19]
error: cannot find symbol
[ERROR] symbol: variable ControllerThreadSocketFactory
[ERROR] location: class DefaultSslProtocolSocketFactory
{code}
We should allow building against hadoop 3.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KYLIN-3033) Provide API compatibility for hbase 2.0 release
[ https://issues.apache.org/jira/browse/KYLIN-3033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16328229#comment-16328229 ] Ted Yu commented on KYLIN-3033: --- hbase 2.0 beta1 has been released. > Provide API compatibility for hbase 2.0 release > --- > > Key: KYLIN-3033 > URL: https://issues.apache.org/jira/browse/KYLIN-3033 > Project: Kylin > Issue Type: Improvement >Reporter: Ted Yu >Priority: Major > Labels: compatibility > > Compiling against hbase 2.0.0-alpha4 release, I got the following compilation > errors: > https://pastebin.com/yfejnTBE > We should start preparing migration to hbase 2.0 compatible APIs. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (KYLIN-3170) Kylin generate wrong cuboids
[ https://issues.apache.org/jira/browse/KYLIN-3170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xingxing Di updated KYLIN-3170: --- Affects Version/s: v1.6.0 > Kylin generate wrong cuboids > > > Key: KYLIN-3170 > URL: https://issues.apache.org/jira/browse/KYLIN-3170 > Project: Kylin > Issue Type: Bug > Components: Job Engine >Affects Versions: v1.6.0, v2.2.0 > Environment: kylin2.2.0, hbase1.2.4 >Reporter: Xingxing Di >Assignee: Shaofeng SHI >Priority: Major > > We have a cube which has 5 dimensions and 2 agg groups: > 5 dimensions : A, B, C, D, E > agg group1 : Mandatory Dimensions (A, B), Hierarchy Dimensions (D, E) > agg group2 : Mandatory Dimensions (A, B), Hierarchy Dimensions (C, E) > > The cube generate 5 cuboids : > > Cuboid 1 > Cuboid 11011 > Cuboid 11010 > Cuboid 11101 > Cuboid 11100 > > there this no cuboid 11000 , I'm confused about this, I think this should be > a bug. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (KYLIN-3170) Kylin generate wrong cuboids
[ https://issues.apache.org/jira/browse/KYLIN-3170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xingxing Di updated KYLIN-3170: --- Summary: Kylin generate wrong cuboids (was: Cuboid wrong) > Kylin generate wrong cuboids > > > Key: KYLIN-3170 > URL: https://issues.apache.org/jira/browse/KYLIN-3170 > Project: Kylin > Issue Type: Bug > Components: Job Engine >Affects Versions: v1.6.0, v2.2.0 > Environment: kylin2.2.0, hbase1.2.4 >Reporter: Xingxing Di >Assignee: Shaofeng SHI >Priority: Major > > We have a cube which has 5 dimensions and 2 agg groups: > 5 dimensions : A, B, C, D, E > agg group1 : Mandatory Dimensions (A, B), Hierarchy Dimensions (D, E) > agg group2 : Mandatory Dimensions (A, B), Hierarchy Dimensions (C, E) > > The cube generate 5 cuboids : > > Cuboid 1 > Cuboid 11011 > Cuboid 11010 > Cuboid 11101 > Cuboid 11100 > > there this no cuboid 11000 , I'm confused about this, I think this should be > a bug. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (KYLIN-3170) Cuboid wrong
[ https://issues.apache.org/jira/browse/KYLIN-3170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xingxing Di updated KYLIN-3170: --- Description: We have a cube which has 5 dimensions and 2 agg groups: 5 dimensions : A, B, C, D, E agg group1 : Mandatory Dimensions (A, B), Hierarchy Dimensions (D, E) agg group2 : Mandatory Dimensions (A, B), Hierarchy Dimensions (C, E) The cube generate 5 cuboids : Cuboid 1 Cuboid 11011 Cuboid 11010 Cuboid 11101 Cuboid 11100 there this no cuboid 11000 , I'm confused about this, I think this should be a bug. was: We have a cube which has 5 dimensions and 2 agg groups: 5 dimensions : A, B, C, D, E agg group1 : Mandatory Dimensions (A, B), Hierarchy Dimensions (D, E) agg group2 : Mandatory Dimensions (A, B), Hierarchy Dimensions (C, E) The cube generate 5 cuboids : | Cuboid 1 | Cuboid 11011| | Cuboid 11010 | Cuboid 11101 | Cuboid 11100 there this no cuboid 11000 , I'm confused about this, I think this should be a bug. > Cuboid wrong > > > Key: KYLIN-3170 > URL: https://issues.apache.org/jira/browse/KYLIN-3170 > Project: Kylin > Issue Type: Bug > Components: Job Engine >Affects Versions: v2.2.0 > Environment: kylin2.2.0, hbase1.2.4 >Reporter: Xingxing Di >Assignee: Shaofeng SHI >Priority: Major > > We have a cube which has 5 dimensions and 2 agg groups: > 5 dimensions : A, B, C, D, E > agg group1 : Mandatory Dimensions (A, B), Hierarchy Dimensions (D, E) > agg group2 : Mandatory Dimensions (A, B), Hierarchy Dimensions (C, E) > > The cube generate 5 cuboids : > > Cuboid 1 > Cuboid 11011 > Cuboid 11010 > Cuboid 11101 > Cuboid 11100 > > there this no cuboid 11000 , I'm confused about this, I think this should be > a bug. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (KYLIN-3170) Cuboid
[ https://issues.apache.org/jira/browse/KYLIN-3170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xingxing Di updated KYLIN-3170: --- Description: We have a cube which has 5 dimensions and 2 agg groups: 5 dimensions : A, B, C, D, E agg group1 : Mandatory Dimensions (A, B), Hierarchy Dimensions (D, E) agg group2 : Mandatory Dimensions (A, B), Hierarchy Dimensions (C, E) The cube generate 5 cuboids : | Cuboid 1 | Cuboid 11011| | Cuboid 11010 | Cuboid 11101 | Cuboid 11100 there this no cuboid 11000 , I'm confused about this, I think this should be a bug. was: We have a cube which has 5 dimensions and 2 agg groups: 5 dimensions : A, B, C, D, E agg group1 : Mandatory Dimensions (A, B), Hierarchy Dimensions (D, E) agg group2 : Mandatory Dimensions (A, B), Hierarchy Dimensions (C, E) The cube generate 5 cuboids : | Cuboid 1 | Cuboid 11011 | Cuboid 11010 | Cuboid 11101 | Cuboid 11100 there this no cuboid 11000 , I'm confused about this, I think this should be a bug. > Cuboid > --- > > Key: KYLIN-3170 > URL: https://issues.apache.org/jira/browse/KYLIN-3170 > Project: Kylin > Issue Type: Bug > Components: Job Engine >Affects Versions: v2.2.0 > Environment: kylin2.2.0, hbase1.2.4 >Reporter: Xingxing Di >Assignee: Shaofeng SHI >Priority: Major > > We have a cube which has 5 dimensions and 2 agg groups: > 5 dimensions : A, B, C, D, E > agg group1 : Mandatory Dimensions (A, B), Hierarchy Dimensions (D, E) > agg group2 : Mandatory Dimensions (A, B), Hierarchy Dimensions (C, E) > > The cube generate 5 cuboids : > | Cuboid 1 > | > Cuboid 11011| > | Cuboid 11010 > | Cuboid 11101 > | Cuboid 11100 > > there this no cuboid 11000 , I'm confused about this, I think this should be > a bug. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (KYLIN-3170) Cuboid wrong
[ https://issues.apache.org/jira/browse/KYLIN-3170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xingxing Di updated KYLIN-3170: --- Summary: Cuboid wrong (was: Cuboid ) > Cuboid wrong > > > Key: KYLIN-3170 > URL: https://issues.apache.org/jira/browse/KYLIN-3170 > Project: Kylin > Issue Type: Bug > Components: Job Engine >Affects Versions: v2.2.0 > Environment: kylin2.2.0, hbase1.2.4 >Reporter: Xingxing Di >Assignee: Shaofeng SHI >Priority: Major > > We have a cube which has 5 dimensions and 2 agg groups: > 5 dimensions : A, B, C, D, E > agg group1 : Mandatory Dimensions (A, B), Hierarchy Dimensions (D, E) > agg group2 : Mandatory Dimensions (A, B), Hierarchy Dimensions (C, E) > > The cube generate 5 cuboids : > | Cuboid 1 > | > Cuboid 11011| > | Cuboid 11010 > | Cuboid 11101 > | Cuboid 11100 > > there this no cuboid 11000 , I'm confused about this, I think this should be > a bug. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (KYLIN-3170) Cuboid
Xingxing Di created KYLIN-3170: -- Summary: Cuboid Key: KYLIN-3170 URL: https://issues.apache.org/jira/browse/KYLIN-3170 Project: Kylin Issue Type: Bug Components: Job Engine Affects Versions: v2.2.0 Environment: kylin2.2.0, hbase1.2.4 Reporter: Xingxing Di Assignee: Shaofeng SHI We have a cube which has 5 dimensions and 2 agg groups: 5 dimensions : A, B, C, D, E agg group1 : Mandatory Dimensions (A, B), Hierarchy Dimensions (D, E) agg group2 : Mandatory Dimensions (A, B), Hierarchy Dimensions (C, E) The cube generate 5 cuboids : | Cuboid 1 | Cuboid 11011 | Cuboid 11010 | Cuboid 11101 | Cuboid 11100 there this no cuboid 11000 , I'm confused about this, I think this should be a bug. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KYLIN-3168) CubeHFileJob should use currentHBaseConfiguration but not new create hbase configuration
[ https://issues.apache.org/jira/browse/KYLIN-3168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16328214#comment-16328214 ] wuyingjun commented on KYLIN-3168: -- !CubeHFileJob_Exception.png! > CubeHFileJob should use currentHBaseConfiguration but not new create hbase > configuration > > > Key: KYLIN-3168 > URL: https://issues.apache.org/jira/browse/KYLIN-3168 > Project: Kylin > Issue Type: Bug >Affects Versions: v2.2.0 >Reporter: wuyingjun >Assignee: wuyingjun >Priority: Major > Attachments: CubeHFileJob_Exception.png > > > CubeHFileJob use new hbase configuration is not correct because when the > zookeeper quorum is not localhost (job worker)， kylin may account zookeeper > ConnectionLossException. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (KYLIN-3168) CubeHFileJob should use currentHBaseConfiguration but not new create hbase configuration
[ https://issues.apache.org/jira/browse/KYLIN-3168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wuyingjun updated KYLIN-3168: - Attachment: CubeHFileJob_Exception.png > CubeHFileJob should use currentHBaseConfiguration but not new create hbase > configuration > > > Key: KYLIN-3168 > URL: https://issues.apache.org/jira/browse/KYLIN-3168 > Project: Kylin > Issue Type: Bug >Affects Versions: v2.2.0 >Reporter: wuyingjun >Assignee: wuyingjun >Priority: Major > Attachments: CubeHFileJob_Exception.png > > > CubeHFileJob use new hbase configuration is not correct because when the > zookeeper quorum is not localhost (job worker)， kylin may account zookeeper > ConnectionLossException. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (KYLIN-3169) Should we simplify DataModelDesc to keep only Joins without defining dimensions & metrics
[
https://issues.apache.org/jira/browse/KYLIN-3169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhong Yanghong updated KYLIN-3169:
--
Description: One important thing kylin does is to materialize Joins between
tables, which is the responsibility of {{DataModelDesc}}. However, is it
necessary to prune or classify columns?
> Should we simplify DataModelDesc to keep only Joins without defining
> dimensions & metrics
> -
>
> Key: KYLIN-3169
> URL: https://issues.apache.org/jira/browse/KYLIN-3169
> Project: Kylin
> Issue Type: Improvement
>Reporter: Zhong Yanghong
>Priority: Major
>
> One important thing kylin does is to materialize Joins between tables, which
> is the responsibility of {{DataModelDesc}}. However, is it necessary to prune
> or classify columns?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (KYLIN-3168) CubeHFileJob should use currentHBaseConfiguration but not new create hbase configuration
[ https://issues.apache.org/jira/browse/KYLIN-3168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wuyingjun updated KYLIN-3168: - Description: CubeHFileJob use new hbase configuration is not correct because when the zookeeper quorum is not localhost (job worker)， kylin may account zookeeper ConnectionLossException. was: CubeHFileJob use new hbase configuration is not correct because when the zookeeper quorum is not localhost， kylin may account zookeeper ConnectionLossException. > CubeHFileJob should use currentHBaseConfiguration but not new create hbase > configuration > > > Key: KYLIN-3168 > URL: https://issues.apache.org/jira/browse/KYLIN-3168 > Project: Kylin > Issue Type: Bug >Affects Versions: v2.2.0 >Reporter: wuyingjun >Assignee: wuyingjun >Priority: Major > > CubeHFileJob use new hbase configuration is not correct because when the > zookeeper quorum is not localhost (job worker)， kylin may account zookeeper > ConnectionLossException. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (KYLIN-3169) Should we simplify DataModelDesc to keep only Joins without defining dimensions & metrics
Zhong Yanghong created KYLIN-3169: - Summary: Should we simplify DataModelDesc to keep only Joins without defining dimensions & metrics Key: KYLIN-3169 URL: https://issues.apache.org/jira/browse/KYLIN-3169 Project: Kylin Issue Type: Improvement Reporter: Zhong Yanghong -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (KYLIN-3168) CubeHFileJob should use currentHBaseConfiguration but not new create hbase configuration
wuyingjun created KYLIN-3168: Summary: CubeHFileJob should use currentHBaseConfiguration but not new create hbase configuration Key: KYLIN-3168 URL: https://issues.apache.org/jira/browse/KYLIN-3168 Project: Kylin Issue Type: Bug Affects Versions: v2.2.0 Reporter: wuyingjun Assignee: wuyingjun CubeHFileJob use new hbase configuration is not correct because when the zookeeper quorum is not localhost， kylin may account zookeeper ConnectionLossException. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (KYLIN-3165) Cannot auto mege segments
[ https://issues.apache.org/jira/browse/KYLIN-3165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaofeng SHI reassigned KYLIN-3165: --- Assignee: Yang Hao (was: Shaofeng SHI) Summary: Cannot auto mege segments (was: cannot auto mege ) > Cannot auto mege segments > - > > Key: KYLIN-3165 > URL: https://issues.apache.org/jira/browse/KYLIN-3165 > Project: Kylin > Issue Type: Bug > Components: Job Engine >Affects Versions: v2.2.0 >Reporter: Yang Hao >Assignee: Yang Hao >Priority: Major > Attachments: KYLIN-3165.apache-master.001.patch > > > The function of auto merge loses efficacy after we upgrade to 2.2.0, related > stack is: > 2018-01-14 11:21:10,965 ERROR [Thread-694] service.CacheService:88 : Error in > updateOnNewSegmentReady() > java.lang.IllegalArgumentException > at com.google.common.base.Preconditions.checkArgument(Preconditions.java:76) > at org.apache.kylin.cube.CubeManager.mergeSegments(CubeManager.java:547) > at > org.apache.kylin.rest.service.CubeService.mergeCubeSegment(CubeService.java:646) > at > org.apache.kylin.rest.service.CubeService.updateOnNewSegmentReady(CubeService.java:594) > at > org.apache.kylin.rest.service.CubeService$$FastClassBySpringCGLIB$$17a07c0e.invoke() > at org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204) > at > org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:669) > at > org.apache.kylin.rest.service.CubeService$$EnhancerBySpringCGLIB$$eaadc7fa.updateOnNewSegmentReady() > at org.apache.kylin.rest.service.CacheService$1$1.run(CacheService.java:86) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KYLIN-3165) cannot auto mege
[ https://issues.apache.org/jira/browse/KYLIN-3165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16327169#comment-16327169 ] Shaofeng SHI commented on KYLIN-3165: - Hi hao and yangcao, Thanks for the reporting. I see the point. It broke the auto merge mechanism, as it always pass a NULL for the tsRange. We will evaluate the impact and determine how to fix. Need to consider both batch and streaming cases. Thanks! > cannot auto mege > - > > Key: KYLIN-3165 > URL: https://issues.apache.org/jira/browse/KYLIN-3165 > Project: Kylin > Issue Type: Bug > Components: Job Engine >Affects Versions: v2.2.0 >Reporter: Yang Hao >Assignee: Shaofeng SHI >Priority: Major > Attachments: KYLIN-3165.apache-master.001.patch > > > The function of auto merge loses efficacy after we upgrade to 2.2.0, related > stack is: > 2018-01-14 11:21:10,965 ERROR [Thread-694] service.CacheService:88 : Error in > updateOnNewSegmentReady() > java.lang.IllegalArgumentException > at com.google.common.base.Preconditions.checkArgument(Preconditions.java:76) > at org.apache.kylin.cube.CubeManager.mergeSegments(CubeManager.java:547) > at > org.apache.kylin.rest.service.CubeService.mergeCubeSegment(CubeService.java:646) > at > org.apache.kylin.rest.service.CubeService.updateOnNewSegmentReady(CubeService.java:594) > at > org.apache.kylin.rest.service.CubeService$$FastClassBySpringCGLIB$$17a07c0e.invoke() > at org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204) > at > org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:669) > at > org.apache.kylin.rest.service.CubeService$$EnhancerBySpringCGLIB$$eaadc7fa.updateOnNewSegmentReady() > at org.apache.kylin.rest.service.CacheService$1$1.run(CacheService.java:86) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KYLIN-3165) cannot auto mege
[ https://issues.apache.org/jira/browse/KYLIN-3165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16327086#comment-16327086 ] yangcao commented on KYLIN-3165: Yes, It is my carelessness, thank you for your reply :) > cannot auto mege > - > > Key: KYLIN-3165 > URL: https://issues.apache.org/jira/browse/KYLIN-3165 > Project: Kylin > Issue Type: Bug > Components: Job Engine >Affects Versions: v2.2.0 >Reporter: Yang Hao >Assignee: Shaofeng SHI >Priority: Major > Attachments: KYLIN-3165.apache-master.001.patch > > > The function of auto merge loses efficacy after we upgrade to 2.2.0, related > stack is: > 2018-01-14 11:21:10,965 ERROR [Thread-694] service.CacheService:88 : Error in > updateOnNewSegmentReady() > java.lang.IllegalArgumentException > at com.google.common.base.Preconditions.checkArgument(Preconditions.java:76) > at org.apache.kylin.cube.CubeManager.mergeSegments(CubeManager.java:547) > at > org.apache.kylin.rest.service.CubeService.mergeCubeSegment(CubeService.java:646) > at > org.apache.kylin.rest.service.CubeService.updateOnNewSegmentReady(CubeService.java:594) > at > org.apache.kylin.rest.service.CubeService$$FastClassBySpringCGLIB$$17a07c0e.invoke() > at org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204) > at > org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:669) > at > org.apache.kylin.rest.service.CubeService$$EnhancerBySpringCGLIB$$eaadc7fa.updateOnNewSegmentReady() > at org.apache.kylin.rest.service.CacheService$1$1.run(CacheService.java:86) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KYLIN-3065) Add 'First' and 'Last' button in case 'Query History' is too much
[ https://issues.apache.org/jira/browse/KYLIN-3065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16326945#comment-16326945 ] Zhixiong Chen commented on KYLIN-3065: -- This patch is fine with me. I will merge it into Kylin master. > Add 'First' and 'Last' button in case 'Query History' is too much > - > > Key: KYLIN-3065 > URL: https://issues.apache.org/jira/browse/KYLIN-3065 > Project: Kylin > Issue Type: Improvement > Components: Web >Reporter: peng.jianhua >Assignee: peng.jianhua >Priority: Minor > Fix For: v2.3.0 > > Attachments: > 0001-KYLIN-3065-Add-First-and-Last-button-in-case-Query-H.patch, 01.png > > > When the 'Query History' or 'Saved Queries' is too much.Just 'Previous' and > 'Next' can not meet the demand. > Such as I just want to find my first query and I've searched too much times,I > need to click to much times to find out. > So I add some attributes for the label 'Pagination'. > The following 01.png is the comparison picture. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KYLIN-3131) After refresh the page,the cubes can't sort by 'create_time'
[ https://issues.apache.org/jira/browse/KYLIN-3131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16326942#comment-16326942 ] Shaofeng SHI commented on KYLIN-3131: - The sorting should happen in the front-end, depending on which property user want to sort. By default it can be the creation time, but also it can be others like name. Making the CubeInstance be comparable and compare by its "createTimeUTC" is not reasonable (how to explain that a Cube is "smaller" than another just because it was created earlier?). It binds the front end behavior with backend entity, which doesn't make sense. > After refresh the page,the cubes can't sort by 'create_time' > > > Key: KYLIN-3131 > URL: https://issues.apache.org/jira/browse/KYLIN-3131 > Project: Kylin > Issue Type: Bug > Components: Web >Reporter: peng.jianhua >Assignee: peng.jianhua >Priority: Minor > Attachments: > 0001-KYLIN-3131-After-refresh-the-page-the-cubes-can-t-so.patch, 01.PNG, > 02.PNG > > > When we open the page 'localhost:7070/kylin/models',the cubes was > disordered.Please refer to 01.png. > Therefore,after we add or clone a new cube,then the page will be refreshed,we > may not find the cube that just add. > And through debug the code,I find that the cubes were sorted by 'create_time' > default.But the cubes' attributes are not contain 'create_time'. > So the cubes were disordered.Please refer to 02.png. > Besides,in the back-end, cubes was sorted by created time from early to > late,so the cubes we get were not latest. > At this time,I add 50 cubes,from c1 to c50,add in order,but the cubes we get > first were c1-c15,not c36-c50. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (KYLIN-3110) The dashboard page has some display problems.
[ https://issues.apache.org/jira/browse/KYLIN-3110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhixiong Chen resolved KYLIN-3110. -- Resolution: Fixed Fix Version/s: v2.3.0 > The dashboard page has some display problems. > - > > Key: KYLIN-3110 > URL: https://issues.apache.org/jira/browse/KYLIN-3110 > Project: Kylin > Issue Type: Bug > Components: Web >Affects Versions: v2.3.0 >Reporter: peng.jianhua >Assignee: peng.jianhua >Priority: Major > Labels: patch > Fix For: v2.3.0 > > Attachments: > 0001-KYLIN-3110-The-dashboard-page-has-some-display-probl.patch, > incomplete_display_and_message_not_right.png > > > The dashboard page has some display problems. > 1. The 'Monthly' and 'Weekly' display incompletely; > 2. The 'showValue' should be 'Show Value'. > refer to [^incomplete_display_and_message_not_right.png] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KYLIN-3110) The dashboard page has some display problems.
[ https://issues.apache.org/jira/browse/KYLIN-3110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16326940#comment-16326940 ] Zhixiong Chen commented on KYLIN-3110: -- I will merge it into Kylin master. Thanks! > The dashboard page has some display problems. > - > > Key: KYLIN-3110 > URL: https://issues.apache.org/jira/browse/KYLIN-3110 > Project: Kylin > Issue Type: Bug > Components: Web >Affects Versions: v2.3.0 >Reporter: peng.jianhua >Assignee: peng.jianhua >Priority: Major > Labels: patch > Fix For: v2.3.0 > > Attachments: > 0001-KYLIN-3110-The-dashboard-page-has-some-display-probl.patch, > incomplete_display_and_message_not_right.png > > > The dashboard page has some display problems. > 1. The 'Monthly' and 'Weekly' display incompletely; > 2. The 'showValue' should be 'Show Value'. > refer to [^incomplete_display_and_message_not_right.png] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KYLIN-2898) Introduce memcached as a distributed cache for queries
[ https://issues.apache.org/jira/browse/KYLIN-2898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16326933#comment-16326933 ] Zhong Yanghong commented on KYLIN-2898: --- https://github.com/apache/kylin/pull/93 > Introduce memcached as a distributed cache for queries > -- > > Key: KYLIN-2898 > URL: https://issues.apache.org/jira/browse/KYLIN-2898 > Project: Kylin > Issue Type: Sub-task > Components: Query Engine >Affects Versions: v2.1.0 >Reporter: Zhong Yanghong >Assignee: Zhong Yanghong >Priority: Major > Fix For: v2.3.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (KYLIN-2898) Introduce memcached as a distributed cache for queries
[ https://issues.apache.org/jira/browse/KYLIN-2898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhong Yanghong updated KYLIN-2898: -- Fix Version/s: v2.3.0 > Introduce memcached as a distributed cache for queries > -- > > Key: KYLIN-2898 > URL: https://issues.apache.org/jira/browse/KYLIN-2898 > Project: Kylin > Issue Type: Sub-task > Components: Query Engine >Affects Versions: v2.1.0 >Reporter: Zhong Yanghong >Assignee: Zhong Yanghong >Priority: Major > Fix For: v2.3.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (KYLIN-2898) Introduce memcached as a distributed cache for queries
[ https://issues.apache.org/jira/browse/KYLIN-2898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhong Yanghong reassigned KYLIN-2898: - Assignee: Zhong Yanghong (was: Wang Ken) > Introduce memcached as a distributed cache for queries > -- > > Key: KYLIN-2898 > URL: https://issues.apache.org/jira/browse/KYLIN-2898 > Project: Kylin > Issue Type: Sub-task > Components: Query Engine >Affects Versions: v2.1.0 >Reporter: Zhong Yanghong >Assignee: Zhong Yanghong >Priority: Major > Fix For: v2.3.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (KYLIN-3159) Remove unnecessary cube access request
[ https://issues.apache.org/jira/browse/KYLIN-3159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhixiong Chen resolved KYLIN-3159. -- Resolution: Fixed Fix Version/s: v2.3.0 > Remove unnecessary cube access request > -- > > Key: KYLIN-3159 > URL: https://issues.apache.org/jira/browse/KYLIN-3159 > Project: Kylin > Issue Type: Bug > Components: Web >Affects Versions: v2.3.0 >Reporter: peng.jianhua >Assignee: peng.jianhua >Priority: Minor > Fix For: v2.3.0 > > Attachments: > 0001-KYLIN-3159-Remove-unnecessary-cube-access-request.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KYLIN-3159) Remove unnecessary cube access request
[ https://issues.apache.org/jira/browse/KYLIN-3159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16326898#comment-16326898 ] Zhixiong Chen commented on KYLIN-3159: -- This patch is fine with me. I will merge it into Kylin master. > Remove unnecessary cube access request > -- > > Key: KYLIN-3159 > URL: https://issues.apache.org/jira/browse/KYLIN-3159 > Project: Kylin > Issue Type: Bug > Components: Web >Affects Versions: v2.3.0 >Reporter: peng.jianhua >Assignee: peng.jianhua >Priority: Minor > Fix For: v2.3.0 > > Attachments: > 0001-KYLIN-3159-Remove-unnecessary-cube-access-request.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KYLIN-3160) Incremental Cube Build
[ https://issues.apache.org/jira/browse/KYLIN-3160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16326894#comment-16326894 ] Zhixiong Chen commented on KYLIN-3160: -- Please don't ask questions in jira. Jira is used to resolve bug or enhancement. You could [use d...@kylin.apache.org|mailto:use%c2%a0...@kylin.apache.org] to ask how to incremental cube. > Incremental Cube Build > -- > > Key: KYLIN-3160 > URL: https://issues.apache.org/jira/browse/KYLIN-3160 > Project: Kylin > Issue Type: Task > Components: Web > Environment: Hadoop, Hive >Reporter: Sandeep Reddy >Priority: Major > > I have a table with Partition Columns 1. Year(2017, 2016 etc) and 2. > Week(01,02,03 till 52) in separate columns, please suggest me how can I build > the cube incrementally??? > I found there are only Date and Timestamp columns available during creation > of model, But I need to build the cube on weekly basis from 1st week to 52nd > week of the year. Please suggest me the configuration for incremental build > of cube on weekly basis according to the week column availble in the table. > How can I schedule the incremental cube build on weekly basis??? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (KYLIN-3162) Fix alignment problem of 'Save Query' pop-up box
[ https://issues.apache.org/jira/browse/KYLIN-3162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhixiong Chen resolved KYLIN-3162. -- Resolution: Fixed Fix Version/s: v2.3.0 > Fix alignment problem of 'Save Query' pop-up box > > > Key: KYLIN-3162 > URL: https://issues.apache.org/jira/browse/KYLIN-3162 > Project: Kylin > Issue Type: Improvement > Components: Web >Affects Versions: v2.2.0, v2.3.0 >Reporter: peng.jianhua >Assignee: peng.jianhua >Priority: Trivial > Fix For: v2.3.0 > > Attachments: > 0001-KYLIN-3162-Fix-alignment-problem-of-Save-Query-pop-u.patch, 01.PNG, > 02.PNG > > > Before: please refer to 01.png. > After: please refer to 02.png. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KYLIN-3162) Fix alignment problem of 'Save Query' pop-up box
[ https://issues.apache.org/jira/browse/KYLIN-3162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16326872#comment-16326872 ] Zhixiong Chen commented on KYLIN-3162: -- This patch is fine with me. I will merge it into Kylin master. > Fix alignment problem of 'Save Query' pop-up box > > > Key: KYLIN-3162 > URL: https://issues.apache.org/jira/browse/KYLIN-3162 > Project: Kylin > Issue Type: Improvement > Components: Web >Affects Versions: v2.2.0, v2.3.0 >Reporter: peng.jianhua >Assignee: peng.jianhua >Priority: Trivial > Attachments: > 0001-KYLIN-3162-Fix-alignment-problem-of-Save-Query-pop-u.patch, 01.PNG, > 02.PNG > > > Before: please refer to 01.png. > After: please refer to 02.png. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KYLIN-2918) Table ACL needs GUI
[ https://issues.apache.org/jira/browse/KYLIN-2918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16326869#comment-16326869 ] Zhixiong Chen commented on KYLIN-2918: -- This patch is fine with me. I will merge it into Kylin master. > Table ACL needs GUI > --- > > Key: KYLIN-2918 > URL: https://issues.apache.org/jira/browse/KYLIN-2918 > Project: Kylin > Issue Type: Bug > Components: Web >Affects Versions: v2.2.0 >Reporter: liyang >Assignee: luguosheng >Priority: Major > Labels: scope > Fix For: v2.3.0 > > Attachments: 0001-KYLIN-2918-table-acl-gui.patch > > > The backend of Table ACL is done, but the GUI part still requires work. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (KYLIN-2918) Table ACL needs GUI
[ https://issues.apache.org/jira/browse/KYLIN-2918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhixiong Chen resolved KYLIN-2918. -- Resolution: Fixed > Table ACL needs GUI > --- > > Key: KYLIN-2918 > URL: https://issues.apache.org/jira/browse/KYLIN-2918 > Project: Kylin > Issue Type: Bug > Components: Web >Affects Versions: v2.2.0 >Reporter: liyang >Assignee: luguosheng >Priority: Major > Labels: scope > Fix For: v2.3.0 > > Attachments: 0001-KYLIN-2918-table-acl-gui.patch > > > The backend of Table ACL is done, but the GUI part still requires work. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
