Details
-
Sub-task
-
Status: Closed
-
Major
-
Resolution: Duplicate
-
None
-
None
-
None
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.