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

[Lefty Leverenz (JIRA)]

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

Lefty Leverenz commented on ORC-54:
---

At least the new ORC configuration parameter (*orc.tolerate.missing.schema*) 
needs to be documented.  But what about the field name functionality?

> 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
> Fix For: 1.2.0
>
>
> 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)

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

[Lefty Leverenz (JIRA)]

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

Lefty Leverenz commented on ORC-54:
---

Should this be documented in the wiki?

> 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
> Fix For: 1.2.0
>
>
> 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)

[jira] [Resolved] (ORC-95) Fix some missing ASF headers

[Owen O'Malley (JIRA)]

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

Owen O'Malley resolved ORC-95.
--
   Resolution: Fixed
Fix Version/s: 1.2.0

> Fix some missing ASF headers
> 
>
> Key: ORC-95
> URL: https://issues.apache.org/jira/browse/ORC-95
> Project: Orc
>  Issue Type: Bug
>Reporter: Owen O'Malley
>Assignee: Owen O'Malley
> Fix For: 1.2.0
>
>
> Some of the new files slipped in without ASF license headers and that should 
> get fixed before the release.



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

[jira] [Resolved] (ORC-93) remove log message about seeking into an empty stream

[Owen O'Malley (JIRA)]

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

Owen O'Malley resolved ORC-93.
--
   Resolution: Fixed
Fix Version/s: 1.2.0

> remove log message about seeking into an empty stream
> -
>
> Key: ORC-93
> URL: https://issues.apache.org/jira/browse/ORC-93
> Project: Orc
>  Issue Type: Bug
>Reporter: Owen O'Malley
>Assignee: Owen O'Malley
> Fix For: 1.2.0
>
>
> Currently the ORC reader complains about seeking to position 0 in an empty 
> stream, but that happens whenever the streams are empty.



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

[jira] [Commented] (ORC-93) remove log message about seeking into an empty stream

[ASF GitHub Bot (JIRA)]

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

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

Github user asfgit closed the pull request at:

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


> remove log message about seeking into an empty stream
> -
>
> Key: ORC-93
> URL: https://issues.apache.org/jira/browse/ORC-93
> Project: Orc
>  Issue Type: Bug
>Reporter: Owen O'Malley
>Assignee: Owen O'Malley
>
> Currently the ORC reader complains about seeking to position 0 in an empty 
> stream, but that happens whenever the streams are empty.



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

[jira] [Commented] (ORC-93) remove log message about seeking into an empty stream

[ASF GitHub Bot (JIRA)]

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

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

Github user omalley commented on the issue:

https://github.com/apache/orc/pull/56
  
I added a test case for the case of having a 0 byte InStream with an empty 
DiskRange in it.


> remove log message about seeking into an empty stream
> -
>
> Key: ORC-93
> URL: https://issues.apache.org/jira/browse/ORC-93
> Project: Orc
>  Issue Type: Bug
>Reporter: Owen O'Malley
>Assignee: Owen O'Malley
>
> Currently the ORC reader complains about seeking to position 0 in an empty 
> stream, but that happens whenever the streams are empty.



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

[jira] [Commented] (ORC-93) remove log message about seeking into an empty stream

[ASF GitHub Bot (JIRA)]

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

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

Github user prasanthj commented on the issue:

https://github.com/apache/orc/pull/56
  
lgtm +1


> remove log message about seeking into an empty stream
> -
>
> Key: ORC-93
> URL: https://issues.apache.org/jira/browse/ORC-93
> Project: Orc
>  Issue Type: Bug
>Reporter: Owen O'Malley
>Assignee: Owen O'Malley
>
> Currently the ORC reader complains about seeking to position 0 in an empty 
> stream, but that happens whenever the streams are empty.



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

[jira] [Commented] (ORC-93) remove log message about seeking into an empty stream

[ASF GitHub Bot (JIRA)]

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

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

GitHub user omalley opened a pull request:

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

ORC-93 Remove log message about seeking into an empty stream.



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

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

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

https://github.com/apache/orc/pull/56.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 #56


commit 6c935f7a1a448ddac9ab9599453a6d3b96ca246e
Author: Owen O'Malley 
Date:   2016-08-16T23:41:55Z

ORC-93 Remove log message about seeking into an empty stream.




> remove log message about seeking into an empty stream
> -
>
> Key: ORC-93
> URL: https://issues.apache.org/jira/browse/ORC-93
> Project: Orc
>  Issue Type: Bug
>Reporter: Owen O'Malley
>Assignee: Owen O'Malley
>
> Currently the ORC reader complains about seeking to position 0 in an empty 
> stream, but that happens whenever the streams are empty.



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

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

[Owen O'Malley (JIRA)]

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

Owen O'Malley resolved ORC-54.
--
   Resolution: Fixed
Fix Version/s: 1.2.0

I just committed this. Thanks, Mark!

> 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
> Fix For: 1.2.0
>
>
> 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)

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

[ASF GitHub Bot (JIRA)]

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

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

Github user asfgit closed the pull request at:

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


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