[jira] [Commented] (KYLIN-3351) Cube Planner not working in apche kylin 2.3.0(open Source)

[praveenece (JIRA)]

[ 
https://issues.apache.org/jira/browse/KYLIN-3351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16463392#comment-16463392
 ] 

praveenece commented on KYLIN-3351:
---

whether its mandatory  to set (build system cubes to collect query
metrics) for Cube planner?



Regards
Praveen.G

On Wed, May 2, 2018 at 1:34 PM, Zhong Yanghong (JIRA) 



> Cube Planner not working in apche kylin 2.3.0(open Source)
> --
>
> Key: KYLIN-3351
> URL: https://issues.apache.org/jira/browse/KYLIN-3351
> Project: Kylin
>  Issue Type: Task
>Reporter: praveenece
>Priority: Major
>
> Hi Team 
>    i want test Cube planner in apache-kylin(2.3.0),So i created cube with 
> segment, and i hit query to cube many times more than thousands but the cube 
> planner there is no change in cuboid level like color changing and not get 
> COUNT in exactly row count and other items.can u please guide me.
> Note:
> Could u tell me?
> Cube Planner Working only old Cube (like 3 month before) or new Cube also.
> Configuration(kylin.Properties)
> kylin.cube.cubeplanner.enabled=true
> Kylin Version=2.3.0(SINGLE  NODE)
> MyCube creation =10days before 
> I referred: http://kylin.apache.org/docs23/howto/howto_use_cube_planner.html
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (KYLIN-3351) Cube Planner not working in apche kylin 2.3.0(open Source)

[praveenece (JIRA)]

[ 
https://issues.apache.org/jira/browse/KYLIN-3351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16463381#comment-16463381
 ] 

praveenece commented on KYLIN-3351:
---

No Zhong

whether its mandatory  (build system cubes to collect query metrics) for Cube 
planner?

 

 

> Cube Planner not working in apche kylin 2.3.0(open Source)
> --
>
> Key: KYLIN-3351
> URL: https://issues.apache.org/jira/browse/KYLIN-3351
> Project: Kylin
>  Issue Type: Task
>Reporter: praveenece
>Priority: Major
>
> Hi Team 
>    i want test Cube planner in apache-kylin(2.3.0),So i created cube with 
> segment, and i hit query to cube many times more than thousands but the cube 
> planner there is no change in cuboid level like color changing and not get 
> COUNT in exactly row count and other items.can u please guide me.
> Note:
> Could u tell me?
> Cube Planner Working only old Cube (like 3 month before) or new Cube also.
> Configuration(kylin.Properties)
> kylin.cube.cubeplanner.enabled=true
> Kylin Version=2.3.0(SINGLE  NODE)
> MyCube creation =10days before 
> I referred: http://kylin.apache.org/docs23/howto/howto_use_cube_planner.html
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (KYLIN-3366) Configure automatic enabling of cubes after a build process

[Pan, Julian (JIRA)]

 [ 
https://issues.apache.org/jira/browse/KYLIN-3366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pan, Julian reassigned KYLIN-3366:
--

Assignee: Pan, Julian

> 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
>
> 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)

[jira] [Updated] (KYLIN-3362) Support dynamic dimension push down

[Zhong Yanghong (JIRA)]

 [ 
https://issues.apache.org/jira/browse/KYLIN-3362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Zhong Yanghong updated KYLIN-3362:
--
Description: 
Here, dynamic dimension is mainly for {{case when}}. By push down, the 
cardinality will be reduced and the returned result row number can be reduced. 
For simplicity, if columns exist in {{then}}, currently we don't do the push 
down.

The same as [KYLIN-3359], the related filters in case when have to be able to 
be pushed down. 

  was:Here, dynamic dimension is mainly for case when for column. By push down, 
the cardinality will be reduced and the returned result row number can be 
reduced.


> Support dynamic dimension push down
> ---
>
> Key: KYLIN-3362
> URL: https://issues.apache.org/jira/browse/KYLIN-3362
> Project: Kylin
>  Issue Type: Sub-task
>Reporter: Zhong Yanghong
>Assignee: Zhong Yanghong
>Priority: Major
>
> Here, dynamic dimension is mainly for {{case when}}. By push down, the 
> cardinality will be reduced and the returned result row number can be 
> reduced. For simplicity, if columns exist in {{then}}, currently we don't do 
> the push down.
> The same as [KYLIN-3359], the related filters in case when have to be able to 
> be pushed down. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (KYLIN-3359) Support sum(expression) if possible

[Zhong Yanghong (JIRA)]

 [ 
https://issues.apache.org/jira/browse/KYLIN-3359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Zhong Yanghong updated KYLIN-3359:
--
Description: 
The expression can be as follows:
 # a ~1~*col ~1~ + a ~2~*col ~2~ + ... + a ~n~*col ~n~ + b, if sum(col 
~1~),sum(col ~2~),...sum(col ~n~) are defined
 # case when {{filter}} ~1~ then expr ~1~
 when {{filter}} ~2~ then expr ~2~
 ...
 else expr ~N~
 end, if {{filter}} ~1~,{{filter}} ~2~, ... {{filter}} ~N-1~, and expr ~1~,expr 
~2~,...expr ~N~ are supported 

There's a constraint for the filter. That is it's able to push down the related 
filters in case when.

  was:
The expression can be as follows:
 # a ~1~*col ~1~ + a ~2~*col ~2~ + ... + a ~n~*col ~n~ + b, if sum(col 
~1~),sum(col ~2~),...sum(col ~n~) are defined
 # case when {{filter}} ~1~ then expr ~1~
 when {{filter}} ~2~ then expr ~2~
 ...
 else expr ~N~
 end, if {{filter}} ~1~,{{filter}} ~2~, ... {{filter}} ~N-1~, and expr ~1~,expr 
~2~,...expr ~N~ are supported 


> Support sum(expression) if possible
> ---
>
> Key: KYLIN-3359
> URL: https://issues.apache.org/jira/browse/KYLIN-3359
> Project: Kylin
>  Issue Type: Sub-task
>Reporter: Zhong Yanghong
>Assignee: Zhong Yanghong
>Priority: Major
>
> The expression can be as follows:
>  # a ~1~*col ~1~ + a ~2~*col ~2~ + ... + a ~n~*col ~n~ + b, if sum(col 
> ~1~),sum(col ~2~),...sum(col ~n~) are defined
>  # case when {{filter}} ~1~ then expr ~1~
>  when {{filter}} ~2~ then expr ~2~
>  ...
>  else expr ~N~
>  end, if {{filter}} ~1~,{{filter}} ~2~, ... {{filter}} ~N-1~, and expr 
> ~1~,expr ~2~,...expr ~N~ are supported 
> There's a constraint for the filter. That is it's able to push down the 
> related filters in case when.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (KYLIN-3365) Add unit test for the coprocessor code, CubeVisitService

[Zhong Yanghong (JIRA)]

 [ 
https://issues.apache.org/jira/browse/KYLIN-3365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Zhong Yanghong updated KYLIN-3365:
--
Description: With this kind of unit test, we can easily verify the logical 
of coprocessor code.

> Add unit test for the coprocessor code, CubeVisitService
> 
>
> Key: KYLIN-3365
> URL: https://issues.apache.org/jira/browse/KYLIN-3365
> Project: Kylin
>  Issue Type: Test
>Reporter: Zhong Yanghong
>Assignee: Zhong Yanghong
>Priority: Major
>
> With this kind of unit test, we can easily verify the logical of coprocessor 
> code.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (KYLIN-3094) Upgrade zookeeper to 3.4.12

[Ted Yu (JIRA)]

[ 
https://issues.apache.org/jira/browse/KYLIN-3094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16463193#comment-16463193
 ] 

Ted Yu commented on KYLIN-3094:
---

3.4.12 has been released.


> Upgrade zookeeper to 3.4.12
> ---
>
> Key: KYLIN-3094
> URL: https://issues.apache.org/jira/browse/KYLIN-3094
> Project: Kylin
>  Issue Type: Improvement
>Reporter: Ted Yu
>Assignee: nichunen
>Priority: Minor
>
> Current zookeeper release is 3.4.12
> We should upgrade dependency from 3.4.8 to 3.4.12 where there is important 
> security fix.
> One such critical fix is ZOOKEEPER-2146, which can be explored maliciously



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (KYLIN-3033) Provide API compatibility for hbase 2.0 release

[Ted Yu (JIRA)]

[ 
https://issues.apache.org/jira/browse/KYLIN-3033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16463194#comment-16463194
 ] 

Ted Yu commented on KYLIN-3033:
---

hbase 2.0 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-2690) Upgrade calcite to release 1.16

[Ted Yu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/KYLIN-2690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ted Yu updated KYLIN-2690:
--
Description: 
Calcite 1.16 has been released.


We should consider upgrading to this release.

  was:
Calcite 1.16 has released.


We should consider upgrading to this release.


> Upgrade calcite to release 1.16
> ---
>
> Key: KYLIN-2690
> URL: https://issues.apache.org/jira/browse/KYLIN-2690
> Project: Kylin
>  Issue Type: Improvement
>Reporter: Ted Yu
>Priority: Major
>
> Calcite 1.16 has been released.
> We should consider upgrading to this release.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (KYLIN-3203) Upgrade Jacoco release

[Ted Yu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/KYLIN-3203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ted Yu updated KYLIN-3203:
--
Description: 
Jacoco is actively maintained by the community.

Here is the latest release:

https://github.com/jacoco/jacoco/releases/tag/v0.8.1

We should upgrade to 0.8.1 release

  was:
Jacoco is actively maintained by the community.

Here is the latest release:
https://github.com/jacoco/jacoco/releases/tag/v0.8.1

We should upgrade to 0.8.1 release


> Upgrade Jacoco release
> --
>
> Key: KYLIN-3203
> URL: https://issues.apache.org/jira/browse/KYLIN-3203
> Project: Kylin
>  Issue Type: Test
>  Components: Tools, Build and Test
>Reporter: Ted Yu
>Assignee: nichunen
>Priority: Minor
>
> Jacoco is actively maintained by the community.
> Here is the latest release:
> https://github.com/jacoco/jacoco/releases/tag/v0.8.1
> We should upgrade to 0.8.1 release



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (KYLIN-3317) Replace UUID.randomUUID with deterministic PRNG

[Ted Yu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/KYLIN-3317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ted Yu updated KYLIN-3317:
--
Description: 
Currently UUID.randomUUID is called in various places in the code base.
* It is non-deterministic.
* It uses a single secure random for UUID generation. This uses a single JVM 
wide lock, and this can lead to lock contention and other performance problems.

We should move to something that is deterministic by using seeded PRNGs

  was:
Currently UUID.randomUUID is called in various places in the code base.
* It is non-deterministic.
* It uses a single secure random for UUID generation. This uses a single JVM 
wide lock, and this can lead to lock contention and other performance problems.


We should move to something that is deterministic by using seeded PRNGs


> Replace UUID.randomUUID with deterministic PRNG
> ---
>
> Key: KYLIN-3317
> URL: https://issues.apache.org/jira/browse/KYLIN-3317
> Project: Kylin
>  Issue Type: Task
>Reporter: Ted Yu
>Assignee: jiatao.tao
>Priority: Major
>
> Currently UUID.randomUUID is called in various places in the code base.
> * It is non-deterministic.
> * It uses a single secure random for UUID generation. This uses a single JVM 
> wide lock, and this can lead to lock contention and other performance 
> problems.
> We should move to something that is deterministic by using seeded PRNGs



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (KYLIN-3290) Avoid calling Class#newInstance

[Ted Yu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/KYLIN-3290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ted Yu updated KYLIN-3290:
--
Description: 
Class#newInstance is deprecated starting in Java 9 - 
https://bugs.openjdk.java.net/browse/JDK-6850612 - because it may throw 
undeclared checked exceptions.


The suggested replacement is getDeclaredConstructor().newInstance(), which 
wraps the checked exceptions in InvocationException.

  was:
Class#newInstance is deprecated starting in Java 9 - 
https://bugs.openjdk.java.net/browse/JDK-6850612 - because it may throw 
undeclared checked exceptions.

The suggested replacement is getDeclaredConstructor().newInstance(), which 
wraps the checked exceptions in InvocationException.


> Avoid calling Class#newInstance
> ---
>
> Key: KYLIN-3290
> URL: https://issues.apache.org/jira/browse/KYLIN-3290
> Project: Kylin
>  Issue Type: Task
>Reporter: Ted Yu
>Assignee: jiatao.tao
>Priority: Minor
>
> Class#newInstance is deprecated starting in Java 9 - 
> https://bugs.openjdk.java.net/browse/JDK-6850612 - because it may throw 
> undeclared checked exceptions.
> The suggested replacement is getDeclaredConstructor().newInstance(), which 
> wraps the checked exceptions in InvocationException.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (KYLIN-3366) Configure automatic enabling of cubes after a build process

[JIRA]

Roberto Tardío Olmos created KYLIN-3366:
---

 Summary: 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


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)