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

Posted to issues@kudu.apache.org by "Mike Percy (JIRA)" <ji...@apache.org> on 2016/02/26 12:49:19 UTC

[jira] [Updated] (KUDU-515) Log-dump, and anything else that acts on logs must handle schema changes mid segment.

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

Mike Percy updated KUDU-515:
----------------------------
    Parent: KUDU-462

> Log-dump, and anything else that acts on logs must handle schema changes mid segment.
> -------------------------------------------------------------------------------------
>
>                 Key: KUDU-515
>                 URL: https://issues.apache.org/jira/browse/KUDU-515
>             Project: Kudu
>          Issue Type: Sub-task
>          Components: log, tablet
>    Affects Versions: M4.5
>            Reporter: Alex Feinberg
>            Assignee: Todd Lipcon
>            Priority: Minor
>
> Currently (see KUDU-508) we log the tablet's schema to the log segment's header. However, a schema may change mid-flight. We need to be able to handle this gracefully.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)