[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=15364713#comment-15364713 ] 

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

Github user omalley commented on a diff in the pull request:

    https://github.com/apache/orc/pull/40#discussion_r69777020
  
    --- Diff: java/core/src/java/org/apache/orc/impl/RecordReaderImpl.java ---
    @@ -27,21 +27,7 @@
     import java.util.List;
     import java.util.Map;
     
    -import org.apache.orc.BooleanColumnStatistics;
    -import org.apache.orc.Reader;
    -import org.apache.orc.RecordReader;
    -import org.apache.orc.TypeDescription;
    -import org.apache.orc.ColumnStatistics;
    -import org.apache.orc.CompressionCodec;
    -import org.apache.orc.DataReader;
    -import org.apache.orc.DateColumnStatistics;
    -import org.apache.orc.DecimalColumnStatistics;
    -import org.apache.orc.DoubleColumnStatistics;
    -import org.apache.orc.IntegerColumnStatistics;
    -import org.apache.orc.OrcConf;
    -import org.apache.orc.StringColumnStatistics;
    -import org.apache.orc.StripeInformation;
    -import org.apache.orc.TimestampColumnStatistics;
    +import org.apache.orc.*;
    --- End diff --
    
    Please configure your IDE to not replace imports with wildcards.


> 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)