[
https://issues.apache.org/jira/browse/KYLIN-1502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
hongbin ma resolved KYLIN-1502.
-------------------------------
Resolution: Fixed
Fix Version/s: v1.5.1
> When cube is not empty, only signature consistent cube desc updates are
> allowed
> -------------------------------------------------------------------------------
>
> Key: KYLIN-1502
> URL: https://issues.apache.org/jira/browse/KYLIN-1502
> Project: Kylin
> Issue Type: Improvement
> Reporter: hongbin ma
> Assignee: hongbin ma
> Fix For: v1.5.1
>
>
> Currently when user update a cube desc, he will be warned that if the update
> causes inconsistency, existing segments might get purged. However users
> never knows ahead whether or not the update is consistent or not, in other
> words, users are not sure what are the effects if they change a specific cube
> desc field.
> For cube desc updates, if the current cube is empty, we'll radically allow
> desc updates even if it will change the signature. On the other side, if the
> cube has existing segments, we'll check signature consistency before allowing
> the update. A failure in signature consistency will return error message and
> no update will be performed.
> this will lead to a less-confusing interactivity with the user.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
