[
https://issues.apache.org/jira/browse/KUDU-860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Todd Lipcon updated KUDU-860:
-----------------------------
Target Version/s: Backlog (was: 1.3.0)
> AlterSchema should log its success or failure in the COMMIT message
> -------------------------------------------------------------------
>
> Key: KUDU-860
> URL: https://issues.apache.org/jira/browse/KUDU-860
> Project: Kudu
> Issue Type: Bug
> Components: tablet
> Affects Versions: Private Beta
> Reporter: Todd Lipcon
> Assignee: Todd Lipcon
> Priority: Critical
>
> Currently, the COMMIT message for alter schema has no information as to
> whether the operation was successful. So, an unsuccessful request to a TS (eg
> with a too-old schema version) will still be replayed during the bootstrap
> replay process. This might be problematic (could end up reverting to an older
> schema, or potentially end up with the wrong schema in the post-bootstrap log
> header)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
