You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kylin.apache.org by "Xiaoxiang Yu (Jira)" <ji...@apache.org> on 2020/07/31 12:03:00 UTC
[jira] [Closed] (KYLIN-3238) Fix NPE when
CubeInstance.getLatestReadySegment() returns null
[ https://issues.apache.org/jira/browse/KYLIN-3238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Xiaoxiang Yu closed KYLIN-3238.
-------------------------------
Resolved in release 3.1.0 (2020-07-03)
> 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
> Fix For: v3.1.0
>
>
> 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
(v8.3.4#803005)