[jira] [Commented] (ORC-54) Evolve schemas based on field name rather than index

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/ORC-54?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15423517#comment-15423517 ] 

ASF GitHub Bot commented on ORC-54:
-----------------------------------

GitHub user omalley opened a pull request:

    https://github.com/apache/orc/pull/55

    ORC-54: Evolve schemas based on field name rather than index

    This is an updated version of Mark's patch that fixes evolution of ACID files and rebases it to the current trunk.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/omalley/orc orc-54

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/orc/pull/55.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #55
    
----
commit e37bc797562f4c219bb733390f8e17a79d7ecec8
Author: Mark Wagner <mw...@apache.org>
Date:   2016-08-16T22:30:51Z

    ORC-54: Evolve schemas based on field name rather than index

----


> Evolve schemas based on field name rather than index
> ----------------------------------------------------
>
>                 Key: ORC-54
>                 URL: https://issues.apache.org/jira/browse/ORC-54
>             Project: Orc
>          Issue Type: Improvement
>            Reporter: Mark Wagner
>            Assignee: Mark Wagner
>
> Schema evolution as it stands today allows adding fields to the end of schemas or removing them from the end. However, because it is based on the index of the column, you can only ever add or remove -- not both.
> ORC files have the full schema information of their contents, so there's actually enough metadata to support changing columns anywhere in the schema.



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