[jira] [Updated] (KYLIN-3238) Fix NPE when CubeInstance.getLatestReadySegment() returns null

2018-02-05 Thread Zhong Yanghong (JIRA) 

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

Zhong Yanghong updated KYLIN-3238:
--
Issue Type: Sub-task  (was: Improvement)
Parent: KYLIN-3237

> Fix NPE when CubeInstance.getLatestReadySegment() returns null
> --
>
> Key: KYLIN-3238
> URL: https://issues.apache.org/jira/browse/KYLIN-3238
> Project: Kylin
>  Issue Type: Sub-task
>Reporter: Zhong Yanghong
>Assignee: Zhong Yanghong
>Priority: Major
>
> Currently we suppose if a cube is in READY status, there should exist READY 
> segments. Then when this kind of cube is selected as a candidate for a query, 
> neither {{getLatestReadySegment}} in {{CubeInstance}} will return null, nor 
> {{cube.getSegments().get(0)}} will throw {{IndexOutOfBoundsException}}.
> However, currently we allow to delete segments by REST API when cube is in 
> READY status, which I think it's not reasonable. To deal with this issue, I 
> propose not to allow segment deletion by REST API when its cube is in READY 
> status.



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

[jira] [Updated] (KYLIN-3238) Fix NPE when CubeInstance.getLatestReadySegment() returns null

2018-02-05 Thread Zhong Yanghong (JIRA) 

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

Zhong Yanghong updated KYLIN-3238:
--
Description: 
Currently we suppose if a cube is in READY status, there should exist READY 
segments. Then when this kind of cube is selected as a candidate for a query, 
neither {{getLatestReadySegment}} in {{CubeInstance}} will return null, nor 
{{cube.getSegments().get(0)}} will throw {{IndexOutOfBoundsException}}.

However, currently we allow to delete segments by REST API when cube is in 
READY status, which I think it's not reasonable. To deal with this issue, I 
propose not to allow segment deletion by REST API when its cube is in READY 
status.

  was:
Currently we suppose if a cube is in READY status, there should exist READY 
segments. Then when this kind of cube is selected as a candidate for a query, 
neither {{getLatestReadySegment}} in {{CubeInstance}} will return null, nor 
{{cube.getSegments().get(0)}} will throw {{IndexOutOfBoundsException}}.

However, there's no validation 


> Fix NPE when CubeInstance.getLatestReadySegment() returns null
> --
>
> Key: KYLIN-3238
> URL: https://issues.apache.org/jira/browse/KYLIN-3238
> Project: Kylin
>  Issue Type: Improvement
>Reporter: Zhong Yanghong
>Assignee: Zhong Yanghong
>Priority: Major
>
> Currently we suppose if a cube is in READY status, there should exist READY 
> segments. Then when this kind of cube is selected as a candidate for a query, 
> neither {{getLatestReadySegment}} in {{CubeInstance}} will return null, nor 
> {{cube.getSegments().get(0)}} will throw {{IndexOutOfBoundsException}}.
> However, currently we allow to delete segments by REST API when cube is in 
> READY status, which I think it's not reasonable. To deal with this issue, I 
> propose not to allow segment deletion by REST API when its cube is in READY 
> status.



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

[jira] [Updated] (KYLIN-3238) Fix NPE when CubeInstance.getLatestReadySegment() returns null

2018-02-05 Thread Zhong Yanghong (JIRA) 

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

Zhong Yanghong updated KYLIN-3238:
--
Description: 
Currently we suppose if a cube is in READY status, there should exist READY 
segments. Then when this kind of cube is selected as a candidate for a query, 
neither {{getLatestReadySegment}} in {{CubeInstance}} will return null, nor 
{{cube.getSegments().get(0)}} will throw {{IndexOutOfBoundsException}}.

However, there's no validation 

  was:Current we suppose {{}}


> Fix NPE when CubeInstance.getLatestReadySegment() returns null
> --
>
> Key: KYLIN-3238
> URL: https://issues.apache.org/jira/browse/KYLIN-3238
> Project: Kylin
>  Issue Type: Improvement
>Reporter: Zhong Yanghong
>Assignee: Zhong Yanghong
>Priority: Major
>
> Currently we suppose if a cube is in READY status, there should exist READY 
> segments. Then when this kind of cube is selected as a candidate for a query, 
> neither {{getLatestReadySegment}} in {{CubeInstance}} will return null, nor 
> {{cube.getSegments().get(0)}} will throw {{IndexOutOfBoundsException}}.
> However, there's no validation 



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

[jira] [Updated] (KYLIN-3238) Fix NPE when CubeInstance.getLatestReadySegment() returns null

2018-02-04 Thread Zhong Yanghong (JIRA) 

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

Zhong Yanghong updated KYLIN-3238:
--
Description: Current we suppose {{}}

> Fix NPE when CubeInstance.getLatestReadySegment() returns null
> --
>
> Key: KYLIN-3238
> URL: https://issues.apache.org/jira/browse/KYLIN-3238
> Project: Kylin
>  Issue Type: Improvement
>Reporter: Zhong Yanghong
>Assignee: Zhong Yanghong
>Priority: Major
>
> Current we suppose {{}}



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