[jira] [Updated] (KYLIN-3540) Improve Mandatory Cuboid Recommendation Algorithm
[
https://issues.apache.org/jira/browse/KYLIN-3540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhong Yanghong updated KYLIN-3540:
--
Description:
Current criteria to recommend mandatory cuboids is based on the average rollup
count collected with query metrics. There's a disadvantage. An example is as
follows:
Cuboid (A,B) has 1000 rows, prebuilt; Cuboid (B) has 10 rows, not prebuilt; The
ground truth for the rollup count from Cuboid (A,B) to Cuboid (B) is
{code}
Cuboid (A,B) - Cuboid (A) = 1000 - 10 = 990
{code}
Suppose B is evenly composed with A. Then for each value of B with A, the row
count is 1000 * (10/100) = 100.
Now for sql
{code}
select B, count(*)
from T
where B = 'e1'
group by B
{code}
Then the rollup count by current algorithm will be
{code}
Cuboid (A,{'e1'}) - return count = 100 - 1 = 99
{code}
which is much smaller than 990 due to the influence of lots of filtered row
count.
It's better to calculate the rollup rate first and then multiple the parent
cuboid row count to estimate the rollup count. The refined formula is as
follows:
{code}
Cuboid (A,B) - Cuboid (A,B) * (return count) / Cuboid (A,{'e1'}) =
1000-1000*1/100 = 990
{code}
Another sql
{code}
select count(*)
from T
where B in {'e1','e2'}
{code}
The rollup count by current algorithm will be
{code}
Cuboid (A,{'e1','e2'}) - return count = 100*2 - 1 = 199
{code}
The rollup count by refined algorithm will be
{code}
Cuboid (A,B) - Cuboid (A,B) * (return count) / Cuboid (A,{'e1','e2'}) =
1000-1000*1/(100*2) = 995
{code}
Above all, the refined algorithm will be much less influenced by filters in sql.
> Improve Mandatory Cuboid Recommendation Algorithm
> -
>
> Key: KYLIN-3540
> URL: https://issues.apache.org/jira/browse/KYLIN-3540
> Project: Kylin
> Issue Type: Improvement
>Reporter: Zhong Yanghong
>Assignee: Zhong Yanghong
>Priority: Major
>
> Current criteria to recommend mandatory cuboids is based on the average
> rollup count collected with query metrics. There's a disadvantage. An example
> is as follows:
> Cuboid (A,B) has 1000 rows, prebuilt; Cuboid (B) has 10 rows, not prebuilt;
> The ground truth for the rollup count from Cuboid (A,B) to Cuboid (B) is
> {code}
> Cuboid (A,B) - Cuboid (A) = 1000 - 10 = 990
> {code}
> Suppose B is evenly composed with A. Then for each value of B with A, the row
> count is 1000 * (10/100) = 100.
> Now for sql
> {code}
> select B, count(*)
> from T
> where B = 'e1'
> group by B
> {code}
> Then the rollup count by current algorithm will be
> {code}
> Cuboid (A,{'e1'}) - return count = 100 - 1 = 99
> {code}
> which is much smaller than 990 due to the influence of lots of filtered row
> count.
> It's better to calculate the rollup rate first and then multiple the parent
> cuboid row count to estimate the rollup count. The refined formula is as
> follows:
> {code}
> Cuboid (A,B) - Cuboid (A,B) * (return count) / Cuboid (A,{'e1'}) =
> 1000-1000*1/100 = 990
> {code}
> Another sql
> {code}
> select count(*)
> from T
> where B in {'e1','e2'}
> {code}
> The rollup count by current algorithm will be
> {code}
> Cuboid (A,{'e1','e2'}) - return count = 100*2 - 1 = 199
> {code}
> The rollup count by refined algorithm will be
> {code}
> Cuboid (A,B) - Cuboid (A,B) * (return count) / Cuboid (A,{'e1','e2'}) =
> 1000-1000*1/(100*2) = 995
> {code}
> Above all, the refined algorithm will be much less influenced by filters in
> sql.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (KYLIN-3445) Upgrade checkstyle version to 8.6
[ https://issues.apache.org/jira/browse/KYLIN-3445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated KYLIN-3445: -- Description: We should upgrade checkstyle version to 8.6+ so that we can use the "match violation message to this regex" feature for suppression. (was: We should upgrade checkstyle version to 8.6+ so that we can use the "match violation message to this regex" feature for suppression . ) > Upgrade checkstyle version to 8.6 > - > > Key: KYLIN-3445 > URL: https://issues.apache.org/jira/browse/KYLIN-3445 > Project: Kylin > Issue Type: Improvement > Components: Tools, Build and Test >Reporter: Ted Yu >Priority: Minor > > We should upgrade checkstyle version to 8.6+ so that we can use the "match > violation message to this regex" feature for suppression. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KYLIN-3520) Deal with NULL values of measures for inmem cubing
[ https://issues.apache.org/jira/browse/KYLIN-3520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16605145#comment-16605145 ] Zhong Yanghong commented on KYLIN-3520: --- Hi [~Shaofengshi], could anyone help review this patch? Thanks a lot. > Deal with NULL values of measures for inmem cubing > -- > > Key: KYLIN-3520 > URL: https://issues.apache.org/jira/browse/KYLIN-3520 > Project: Kylin > Issue Type: Improvement > Components: Job Engine >Reporter: Zhong Yanghong >Assignee: Zhong Yanghong >Priority: Major > Fix For: v2.5.0 > > Attachments: APACHE-KYLIN-3520.patch > > > Previously NULL values will be dealt for dimensions during both layered > cubing and inmem cubing. However, NULL values of measures only are dealt for > layered cubing. NULL values of measures for inmem cubing also should be dealt > with. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (KYLIN-3520) Deal with NULL values of measures for inmem cubing
[ https://issues.apache.org/jira/browse/KYLIN-3520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhong Yanghong updated KYLIN-3520: -- Component/s: Job Engine > Deal with NULL values of measures for inmem cubing > -- > > Key: KYLIN-3520 > URL: https://issues.apache.org/jira/browse/KYLIN-3520 > Project: Kylin > Issue Type: Improvement > Components: Job Engine >Reporter: Zhong Yanghong >Assignee: Zhong Yanghong >Priority: Major > Fix For: v2.5.0 > > Attachments: APACHE-KYLIN-3520.patch > > > Previously NULL values will be dealt for dimensions during both layered > cubing and inmem cubing. However, NULL values of measures only are dealt for > layered cubing. NULL values of measures for inmem cubing also should be dealt > with. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (KYLIN-3520) Deal with NULL values of measures for inmem cubing
[ https://issues.apache.org/jira/browse/KYLIN-3520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhong Yanghong updated KYLIN-3520: -- Description: Previously NULL values will be dealt for dimensions during both layered cubing and inmem cubing. However, NULL values of measures only are dealt for layered cubing. NULL values of measures for inmem cubing also should be dealt with. > Deal with NULL values of measures for inmem cubing > -- > > Key: KYLIN-3520 > URL: https://issues.apache.org/jira/browse/KYLIN-3520 > Project: Kylin > Issue Type: Improvement >Reporter: Zhong Yanghong >Assignee: Zhong Yanghong >Priority: Major > Fix For: v2.5.0 > > Attachments: APACHE-KYLIN-3520.patch > > > Previously NULL values will be dealt for dimensions during both layered > cubing and inmem cubing. However, NULL values of measures only are dealt for > layered cubing. NULL values of measures for inmem cubing also should be dealt > with. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (KYLIN-3520) Deal with NULL values of measures for inmem cubing
[ https://issues.apache.org/jira/browse/KYLIN-3520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhong Yanghong updated KYLIN-3520: -- Attachment: APACHE-KYLIN-3520.patch > Deal with NULL values of measures for inmem cubing > -- > > Key: KYLIN-3520 > URL: https://issues.apache.org/jira/browse/KYLIN-3520 > Project: Kylin > Issue Type: Improvement >Reporter: Zhong Yanghong >Assignee: Zhong Yanghong >Priority: Major > Fix For: v2.5.0 > > Attachments: APACHE-KYLIN-3520.patch > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KYLIN-3521) Enable Cube Planner by default
[ https://issues.apache.org/jira/browse/KYLIN-3521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16605100#comment-16605100 ] ASF subversion and git services commented on KYLIN-3521: Commit 6d00ed556c192fe498df4e265bce6ef4bb969e0b in kylin's branch refs/heads/master from shaofengshi [ https://gitbox.apache.org/repos/asf?p=kylin.git;h=6d00ed5 ] KYLIN-3521 fix ut > Enable Cube Planner by default > -- > > Key: KYLIN-3521 > URL: https://issues.apache.org/jira/browse/KYLIN-3521 > Project: Kylin > Issue Type: Improvement >Affects Versions: v2.5.0 >Reporter: Shaofeng SHI >Assignee: Ma Gang >Priority: Minor > Fix For: v2.5.0 > > Attachments: KYLIN-3521_V2.patch, KYLIN-3521_V3.patch > > > Cube planner can significantly reduce the cuboid number that to build. As it > wasn't enabled by default in 2.3 and 2.4, many users don't know that. > > To let more user to start using it, I suggest to enable it by default. > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KYLIN-3521) Enable Cube Planner by default
[ https://issues.apache.org/jira/browse/KYLIN-3521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16605086#comment-16605086 ] ASF subversion and git services commented on KYLIN-3521: Commit 8349747cad1ccfb159a152e11a5023a4e8a37f17 in kylin's branch refs/heads/2.5.x from shaofengshi [ https://gitbox.apache.org/repos/asf?p=kylin.git;h=8349747 ] KYLIN-3521 fix ut > Enable Cube Planner by default > -- > > Key: KYLIN-3521 > URL: https://issues.apache.org/jira/browse/KYLIN-3521 > Project: Kylin > Issue Type: Improvement >Affects Versions: v2.5.0 >Reporter: Shaofeng SHI >Assignee: Ma Gang >Priority: Minor > Fix For: v2.5.0 > > Attachments: KYLIN-3521_V2.patch, KYLIN-3521_V3.patch > > > Cube planner can significantly reduce the cuboid number that to build. As it > wasn't enabled by default in 2.3 and 2.4, many users don't know that. > > To let more user to start using it, I suggest to enable it by default. > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (KYLIN-3484) Update Hadoop version to 2.7.7
[ https://issues.apache.org/jira/browse/KYLIN-3484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu updated KYLIN-3484: -- Description: We should upgrade the Hadoop 2.7 dependency to 2.7.7, to pick up bug and security fixes . (was: We should upgrade the Hadoop 2.7 dependency to 2.7.7, to pick up bug and security fixes.) > Update Hadoop version to 2.7.7 > -- > > Key: KYLIN-3484 > URL: https://issues.apache.org/jira/browse/KYLIN-3484 > Project: Kylin > Issue Type: Task >Reporter: Ted Yu >Priority: Minor > > We should upgrade the Hadoop 2.7 dependency to 2.7.7, to pick up bug and > security fixes . -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (KYLIN-3541) TableACLManagerTest failed
[
https://issues.apache.org/jira/browse/KYLIN-3541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yichen Zhou updated KYLIN-3541:
---
Description:
2018-09-05 11:11:27,013 ERROR [pool-179-thread-1] cachesync.Broadcaster:137 :
Announce broadcast event failed, targetNode localhost:49607 broadcastEvent
BroadcastEvent\{entity=table_acl, event=create, cacheKey=default}, error msg:
org.apache.http.conn.HttpHostConnectException: Connection to
[http://localhost:49607|http://localhost:49607/]
refused 2018-09-05 11:11:27,013 ERROR [pool-179-thread-1]
cachesync.Broadcaster:330 : Announce broadcast event exceeds retry limit,
abandon targetNode localhost:49607 broadcastEvent
BroadcastEvent\{entity=table_acl, event=create, cacheKey=default} 2018-09-05
11:11:27,015 INFO [main] server.AbstractConnector:318 : Stopped
ServerConnector@664c7565{HTTP/1.1,[http/1.1]}
{0.0.0.0:49607}
2018-09-05 11:11:27,015 INFO [main] handler.ContextHandler:910 : Stopped
o.e.j.s.ServletContextHandler@515a8659\{/,null,UNAVAILABLE} 2018-09-05
11:11:27,026 INFO [main] common.KylinConfig:113 : Destroy KylinConfig [ERROR]
Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 2.932 s <<<
FAILURE! - in org.apache.kylin.rest.security.TableACLManagerTest [ERROR]
test(org.apache.kylin.rest.security.TableACLManagerTest) Time elapsed: 2.856 s
<<< FAILURE! java.lang.AssertionError: expected:<1> but was:<0> at
org.apache.kylin.rest.security.TableACLManagerTest.test(TableACLManagerTest.java:50)
mvn test in sandbox:
2018-09-05 12:09:20,203 DEBUG [Thread-3] util.ZookeeperDistributedLock:223 :
31...@sandbox.hortonworks.com trying to unlock
/kylin/../examples/test_metadata/job_engine/global_job_engine_lock
Exception in thread "Thread-3" java.lang.RuntimeException: Error while peeking
at /kylin/../examples/test_metadata/job_engine/global_job_engine_lock
at
org.apache.kylin.storage.hbase.util.ZookeeperDistributedLock.peekLock(ZookeeperDistributedLock.java:205)
at
org.apache.kylin.storage.hbase.util.ZookeeperDistributedLock.unlock(ZookeeperDistributedLock.java:225)
at
org.apache.kylin.storage.hbase.util.ZookeeperDistributedLock.unlockJobEngine(ZookeeperDistributedLock.java:312)
at
org.apache.kylin.storage.hbase.util.ZookeeperJobLock.unlockJobEngine(ZookeeperJobLock.java:86)
at
org.apache.kylin.job.impl.threadpool.DefaultScheduler.shutdown(DefaultScheduler.java:194)
at org.apache.kylin.rest.service.JobService$2.run(JobService.java:143)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.IllegalStateException: instance must be started before
calling this method
at
org.apache.curator.shaded.com.google.common.base.Preconditions.checkState(Preconditions.java:176)
at
org.apache.curator.framework.imps.CuratorFrameworkImpl.getData(CuratorFrameworkImpl.java:375)
at
org.apache.kylin.storage.hbase.util.ZookeeperDistributedLock.peekLock(ZookeeperDistributedLock.java:200)
... 6 more
was:
2018-09-05 11:11:27,013 ERROR [pool-179-thread-1] cachesync.Broadcaster:137 :
Announce broadcast event failed, targetNode localhost:49607 broadcastEvent
BroadcastEvent\{entity=table_acl, event=create, cacheKey=default}, error msg:
org.apache.http.conn.HttpHostConnectException: Connection to
[http://localhost:49607|http://localhost:49607/]
refused 2018-09-05 11:11:27,013 ERROR [pool-179-thread-1]
cachesync.Broadcaster:330 : Announce broadcast event exceeds retry limit,
abandon targetNode localhost:49607 broadcastEvent
BroadcastEvent\{entity=table_acl, event=create, cacheKey=default} 2018-09-05
11:11:27,015 INFO [main] server.AbstractConnector:318 : Stopped
ServerConnector@664c7565\{HTTP/1.1,[http/1.1]}{0.0.0.0:49607} 2018-09-05
11:11:27,015 INFO [main] handler.ContextHandler:910 : Stopped
o.e.j.s.ServletContextHandler@515a8659\{/,null,UNAVAILABLE} 2018-09-05
11:11:27,026 INFO [main] common.KylinConfig:113 : Destroy KylinConfig [ERROR]
Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 2.932 s <<<
FAILURE! - in org.apache.kylin.rest.security.TableACLManagerTest [ERROR]
test(org.apache.kylin.rest.security.TableACLManagerTest) Time elapsed: 2.856 s
<<< FAILURE! java.lang.AssertionError: expected:<1> but was:<0> at
org.apache.kylin.rest.security.TableACLManagerTest.test(TableACLManagerTest.java:50)
> TableACLManagerTest failed
> --
>
> Key: KYLIN-3541
> URL: https://issues.apache.org/jira/browse/KYLIN-3541
> Project: Kylin
> Issue Type: Bug
>Reporter: Yichen Zhou
>Priority: Major
>
> 2018-09-05 11:11:27,013 ERROR [pool-179-thread-1] cachesync.Broadcaster:137 :
> Announce broadcast event failed, targetNode localhost:49607 broadcastEvent
> BroadcastEvent\{entity=table_acl, event=create, cacheKey=default}, error msg:
> org.apache.http.conn.HttpHostConnectException: Connection to
> [http://localhost:49607|http://localhost:49607/]
> refused
[jira] [Created] (KYLIN-3541) TableACLManagerTest failed
Yichen Zhou created KYLIN-3541:
--
Summary: TableACLManagerTest failed
Key: KYLIN-3541
URL: https://issues.apache.org/jira/browse/KYLIN-3541
Project: Kylin
Issue Type: Bug
Reporter: Yichen Zhou
2018-09-05 11:11:27,013 ERROR [pool-179-thread-1] cachesync.Broadcaster:137 :
Announce broadcast event failed, targetNode localhost:49607 broadcastEvent
BroadcastEvent\{entity=table_acl, event=create, cacheKey=default}, error msg:
org.apache.http.conn.HttpHostConnectException: Connection to
[http://localhost:49607|http://localhost:49607/]
refused 2018-09-05 11:11:27,013 ERROR [pool-179-thread-1]
cachesync.Broadcaster:330 : Announce broadcast event exceeds retry limit,
abandon targetNode localhost:49607 broadcastEvent
BroadcastEvent\{entity=table_acl, event=create, cacheKey=default} 2018-09-05
11:11:27,015 INFO [main] server.AbstractConnector:318 : Stopped
ServerConnector@664c7565\{HTTP/1.1,[http/1.1]}{0.0.0.0:49607} 2018-09-05
11:11:27,015 INFO [main] handler.ContextHandler:910 : Stopped
o.e.j.s.ServletContextHandler@515a8659\{/,null,UNAVAILABLE} 2018-09-05
11:11:27,026 INFO [main] common.KylinConfig:113 : Destroy KylinConfig [ERROR]
Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 2.932 s <<<
FAILURE! - in org.apache.kylin.rest.security.TableACLManagerTest [ERROR]
test(org.apache.kylin.rest.security.TableACLManagerTest) Time elapsed: 2.856 s
<<< FAILURE! java.lang.AssertionError: expected:<1> but was:<0> at
org.apache.kylin.rest.security.TableACLManagerTest.test(TableACLManagerTest.java:50)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (KYLIN-3539) Hybrid segment overlap not cover some case
[ https://issues.apache.org/jira/browse/KYLIN-3539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chao Long updated KYLIN-3539: - Description: now Hybrid uses every cube's latest segment to check whether overlap exists, but it can't cover all cases. example: hybrid: cube1: segment1: range(2012-01-01, 2012-01-02) cube2: segment1: range(2012-01-01, 2012-01-02) segment2: range(2012-01-03, 2012-01-04) this hybrid has overlap segment range(2012-01-01, 2012-01-02), but the program can not find out. > Hybrid segment overlap not cover some case > -- > > Key: KYLIN-3539 > URL: https://issues.apache.org/jira/browse/KYLIN-3539 > Project: Kylin > Issue Type: Improvement >Reporter: Chao Long >Assignee: Chao Long >Priority: Major > Fix For: v2.5.0 > > > now Hybrid uses every cube's latest segment to check whether overlap exists, > but it can't cover all cases. > example: > hybrid: > cube1: > segment1: range(2012-01-01, 2012-01-02) > cube2: > segment1: range(2012-01-01, 2012-01-02) > segment2: range(2012-01-03, 2012-01-04) > this hybrid has overlap segment range(2012-01-01, 2012-01-02), but the > program can not find out. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KYLIN-3521) Enable Cube Planner by default
[ https://issues.apache.org/jira/browse/KYLIN-3521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16604157#comment-16604157 ] Zhong Yanghong commented on KYLIN-3521: --- Hi [~Aron.tao] and [~Shaofengshi], what's the meaning of *getPropertiesWhiteList()* in *KylinConfigBase* ? Why *kylin.cube.cubeplanner.enabled* and *web.dashboard-enabled* are added? What's the criteria for those properties added? > Enable Cube Planner by default > -- > > Key: KYLIN-3521 > URL: https://issues.apache.org/jira/browse/KYLIN-3521 > Project: Kylin > Issue Type: Improvement >Affects Versions: v2.5.0 >Reporter: Shaofeng SHI >Assignee: Ma Gang >Priority: Minor > Fix For: v2.5.0 > > Attachments: KYLIN-3521_V2.patch, KYLIN-3521_V3.patch > > > Cube planner can significantly reduce the cuboid number that to build. As it > wasn't enabled by default in 2.3 and 2.4, many users don't know that. > > To let more user to start using it, I suggest to enable it by default. > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KYLIN-3521) Enable Cube Planner by default
[ https://issues.apache.org/jira/browse/KYLIN-3521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16604139#comment-16604139 ] Ma Gang commented on KYLIN-3521: Add another patch KYLIN-3521_V3.patch to fix. Since Shaofeng is busy now, [~yaho] could you help to apply the patch. > Enable Cube Planner by default > -- > > Key: KYLIN-3521 > URL: https://issues.apache.org/jira/browse/KYLIN-3521 > Project: Kylin > Issue Type: Improvement >Affects Versions: v2.5.0 >Reporter: Shaofeng SHI >Assignee: Ma Gang >Priority: Minor > Fix For: v2.5.0 > > Attachments: KYLIN-3521_V2.patch, KYLIN-3521_V3.patch > > > Cube planner can significantly reduce the cuboid number that to build. As it > wasn't enabled by default in 2.3 and 2.4, many users don't know that. > > To let more user to start using it, I suggest to enable it by default. > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Reopened] (KYLIN-3521) Enable Cube Planner by default
[ https://issues.apache.org/jira/browse/KYLIN-3521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ma Gang reopened KYLIN-3521: > Enable Cube Planner by default > -- > > Key: KYLIN-3521 > URL: https://issues.apache.org/jira/browse/KYLIN-3521 > Project: Kylin > Issue Type: Improvement >Affects Versions: v2.5.0 >Reporter: Shaofeng SHI >Assignee: Ma Gang >Priority: Minor > Fix For: v2.5.0 > > Attachments: KYLIN-3521_V2.patch, KYLIN-3521_V3.patch > > > Cube planner can significantly reduce the cuboid number that to build. As it > wasn't enabled by default in 2.3 and 2.4, many users don't know that. > > To let more user to start using it, I suggest to enable it by default. > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (KYLIN-3521) Enable Cube Planner by default
[ https://issues.apache.org/jira/browse/KYLIN-3521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ma Gang updated KYLIN-3521: --- Attachment: KYLIN-3521_V3.patch > Enable Cube Planner by default > -- > > Key: KYLIN-3521 > URL: https://issues.apache.org/jira/browse/KYLIN-3521 > Project: Kylin > Issue Type: Improvement >Affects Versions: v2.5.0 >Reporter: Shaofeng SHI >Assignee: Ma Gang >Priority: Minor > Fix For: v2.5.0 > > Attachments: KYLIN-3521_V2.patch, KYLIN-3521_V3.patch > > > Cube planner can significantly reduce the cuboid number that to build. As it > wasn't enabled by default in 2.3 and 2.4, many users don't know that. > > To let more user to start using it, I suggest to enable it by default. > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KYLIN-3521) Enable Cube Planner by default
[ https://issues.apache.org/jira/browse/KYLIN-3521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16604115#comment-16604115 ] Ma Gang commented on KYLIN-3521: Thanks [~yichen.zhou], my bad. Why we need to check the configuration value in UT? I don't think it make any sense. Thought this patch is just make a simple configuration change..., anyway I will fix it and provide another patch. > Enable Cube Planner by default > -- > > Key: KYLIN-3521 > URL: https://issues.apache.org/jira/browse/KYLIN-3521 > Project: Kylin > Issue Type: Improvement >Affects Versions: v2.5.0 >Reporter: Shaofeng SHI >Assignee: Ma Gang >Priority: Minor > Fix For: v2.5.0 > > Attachments: KYLIN-3521_V2.patch > > > Cube planner can significantly reduce the cuboid number that to build. As it > wasn't enabled by default in 2.3 and 2.4, many users don't know that. > > To let more user to start using it, I suggest to enable it by default. > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (KYLIN-3539) Hybrid segment overlap not cover some case
Chao Long created KYLIN-3539: Summary: Hybrid segment overlap not cover some case Key: KYLIN-3539 URL: https://issues.apache.org/jira/browse/KYLIN-3539 Project: Kylin Issue Type: Improvement Reporter: Chao Long Assignee: Chao Long Fix For: v2.5.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (KYLIN-3529) Prompt not friendly
[ https://issues.apache.org/jira/browse/KYLIN-3529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chao Long updated KYLIN-3529: - Fix Version/s: v2.5.0 > Prompt not friendly > --- > > Key: KYLIN-3529 > URL: https://issues.apache.org/jira/browse/KYLIN-3529 > Project: Kylin > Issue Type: Bug > Components: Web >Reporter: Na Zhai >Assignee: Chao Long >Priority: Major > Fix For: v2.5.0 > > > *Scene 1：*When I create a hybrid with duplicate name, then I click submit, > the error message "error execute org.apache.kylin.rest.job.HybridCubeCLI" > will pop up. > > *Scene 2：*When I create a hybrid with duplicate date/time cube, then I click > submit, the error message "error execute > org.apache.kylin.rest.job.HybridCubeCLI" will pop up. > > I think the error message should be more friendly. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (KYLIN-3538) Automatic cube enabled functionality is not merged into 2.4.0
Iñigo Martinez created KYLIN-3538: - Summary: Automatic cube enabled functionality is not merged into 2.4.0 Key: KYLIN-3538 URL: https://issues.apache.org/jira/browse/KYLIN-3538 Project: Kylin Issue Type: Bug Components: Job Engine Affects Versions: v2.4.0 Reporter: Iñigo Martinez This functionality that was scheduled for version 2.4.0 finally was not included in proper release. [https://jira.apache.org/jira/browse/KYLIN-3366|https://jira.apache.org/jira/browse/KYLIN-3366] Checking source code show us that is missing. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KYLIN-3366) Configure automatic enabling of cubes after a build process
[ https://issues.apache.org/jira/browse/KYLIN-3366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16604022#comment-16604022 ] Iñigo Martinez commented on KYLIN-3366: --- Hi. This property has not been added to Kylin 2.4.0. Currently this option is not available and checking souce code for version 2.4.0 is also missing. > Configure automatic enabling of cubes after a build process > --- > > Key: KYLIN-3366 > URL: https://issues.apache.org/jira/browse/KYLIN-3366 > Project: Kylin > Issue Type: New Feature >Affects Versions: v2.3.1 > Environment: Kylin 2.3.1 and Hadoop EMR 5.7 >Reporter: Roberto Tardío Olmos >Assignee: Pan, Julian >Priority: Minor > Labels: features > Fix For: v2.4.0 > > Attachments: KYLIN-3366.patch > > > Kylin automatically enables the disabled cubes after a construction process. > This behavior forces us to constantly disable a new cube that is under > development to replace an existing and enabled cube. If we do not disable it, > we could have problems with the routing of the queries. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
