You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@kudu.apache.org by "Andrew Wong (JIRA)" <ji...@apache.org> on 2019/03/04 23:46:00 UTC

[jira] [Resolved] (KUDU-860) AlterSchema should log its success or failure in the COMMIT message

     [ https://issues.apache.org/jira/browse/KUDU-860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrew Wong resolved KUDU-860.
------------------------------
       Resolution: Fixed
    Fix Version/s: 1.9.0

Fixed in 16d9a863d0f31069965aee1a71912a65339a4160

> 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: Major
>             Fix For: 1.9.0
>
>
> 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
(v7.6.3#76005)