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

[Billy Liu (JIRA)]

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

Billy Liu commented on KYLIN-3351:
--

Hello [~praveenece], could you join the Kylin user mailer and send your 
questions there?

By the way, 2.3.0 is not suggested, please upgrade to 2.3.1

> 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] [Created] (KYLIN-3356) Constant in SecretKeySpec

[liyang (JIRA)]

liyang created KYLIN-3356:
-

 Summary: Constant in SecretKeySpec
 Key: KYLIN-3356
 URL: https://issues.apache.org/jira/browse/KYLIN-3356
 Project: Kylin
  Issue Type: Improvement
Reporter: liyang


Reported by Rumen Paletov : 


 As part of some research about the common crypto mistakes that developers
 make <[https://cs.ucsb.edu/~chris/research/doc/ccs13_cryptolint.pdf]>, I
 noticed that your application has one of them.
 
 In particular, there's a violation of Rule 3 in
 org.apache.kylin.common.util.EncryptUtil
 
<[https://github.com/apache/kylin/blob/5552164ba09eba989b9ddccdf3f1e4f83ed0b799/core-common/src/main/java/org/apache/kylin/common/util/EncryptUtil.java#L36]>.
 That is, SecretKeySpec is being initialized with a constant key
 
<[https://github.com/apache/kylin/blob/5552164ba09eba989b9ddccdf3f1e4f83ed0b799/core-common/src/main/java/org/apache/kylin/common/util/EncryptUtil.java#L30]>
 instead of a randomly generated one.
 
 One solution would be to generate a key using SecureRandom:
 
 > byte[] key = new byte[16];
 > new SecureRandom.nextBytes(key);
 
 



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

[jira] [Commented] (KYLIN-3335) Add project & cube related info to the job id for better filtering

[liyang (JIRA)]

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

liyang commented on KYLIN-3335:
---

+1 for upgrade, prefer simpler approach  :)

> Add project & cube related info to the job id for better filtering
> --
>
> Key: KYLIN-3335
> URL: https://issues.apache.org/jira/browse/KYLIN-3335
> Project: Kylin
>  Issue Type: Improvement
>Reporter: Zhong Yanghong
>Priority: Major
>
> Currently it's painful to search cube or project related jobs, since those 
> infos are hidden in values. Especially, when users want to list job in a 
> period under one project, by current design, all of the job output info have 
> to be read into memory. If this kind of operation is done very often within a 
> short period, it's easy to get OOM.
> If the job id is prefixed with project and cube names, then we can push down 
> prefix filters, which is efficient and safe.
> This kind of change will cause backward compatibility issue. There're two 
> ways to deal with this:
> * Set a milestone with time tag, if a search relates to data earlier than 
> this time, then just need to do one scan with prefix filter. Otherwise, two 
> scans are needed. One with prefix filter and the other use current strategy. 
> As time goes on, old job infos will be deleted. Once there's no data older 
> than the time, only one scan is needed.
> * Do migration for the old data once.



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

[jira] [Commented] (KYLIN-3308) Improvement exception in REST

[liyang (JIRA)]

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

liyang commented on KYLIN-3308:
---

Nice proposal~

> Improvement exception in REST
> -
>
> Key: KYLIN-3308
> URL: https://issues.apache.org/jira/browse/KYLIN-3308
> Project: Kylin
>  Issue Type: Improvement
>  Components: REST Service
>Reporter: Pan, Julian
>Assignee: Pan, Julian
>Priority: Major
>
> There are kinds of exception throw by rest call, and we need better defined 
> the exception. 
> For example:
> 1> There are three types of exception for cube equals null in CubeController:
> NotFoundException (deleteCube)
> InternalErrorException(getCube)
> BadRequestException (cloneCube)
> 2> And sometimes InternalErrorException will warp the BadRequestException in 
> CubeController.saveCubeDesc
>  



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