Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
Description
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.