[
https://issues.apache.org/jira/browse/KUDU-515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17118853#comment-17118853
]
Grant Henke commented on KUDU-515:
----------------------------------
It looks like this was resolved with the following commits:
* https://github.com/apache/kudu/commit/b0f5bfd9a3f81a7e9a2305b7a3a63e898026a11f
* https://github.com/apache/kudu/commit/6d47a476d1286bc9f2b9fa7546cd8a53d84b14ee
* https://github.com/apache/kudu/commit/a1e44477ce10b34ca8b8a2f8bb4f9c17f75c2ad2
* https://github.com/apache/kudu/commit/36fd7e05ab0926bdd18a5fb42b601d9dd7a970b8
> 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
(v8.3.4#803005)
