[jira] [Commented] (PARQUET-815) Unable to create parquet file for the given data

2017-01-09 Thread Ryan Blue (JIRA)
[ https://issues.apache.org/jira/browse/PARQUET-815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15813430#comment-15813430 ] Ryan Blue commented on PARQUET-815: --- Looks like a problem with schema inference in Spark. Precision

[jira] [Resolved] (PARQUET-815) Unable to create parquet file for the given data

2017-01-09 Thread Ryan Blue (JIRA)
[ https://issues.apache.org/jira/browse/PARQUET-815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryan Blue resolved PARQUET-815. --- Resolution: Not A Problem > Unable to create parquet file for the given data >

[jira] [Created] (PARQUET-828) [C++] "version" field set improperly in file metadata

2017-01-09 Thread Wes McKinney (JIRA)
Wes McKinney created PARQUET-828: Summary: [C++] "version" field set improperly in file metadata Key: PARQUET-828 URL: https://issues.apache.org/jira/browse/PARQUET-828 Project: Parquet

Re: 1.8.2 patch release

2017-01-09 Thread Ryan Blue
I posted a note on the Spark list pointing to this thread. I also know most of the issues that they're interested in fixing, so I've marked those on the backports doc. We should also do a benchmark to compare 1.8.1 with 1.8.2 to ensure we don't have a performance regression. rb On Fri, Jan 6,

Re: 1.8.2 patch release

2017-01-09 Thread Cheng Lian
Already reviewed the list and left comments on the spreadsheet. The current list LGTM. Thanks Ryan for doing this! Cheng On 1/9/17 1:36 PM, Ryan Blue wrote: I posted a note on the Spark list pointing to this thread. I also know most of the issues that they're interested in fixing, so I've

[jira] [Resolved] (PARQUET-828) [C++] "version" field set improperly in file metadata

2017-01-09 Thread Uwe L. Korn (JIRA)
[ https://issues.apache.org/jira/browse/PARQUET-828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uwe L. Korn resolved PARQUET-828. - Resolution: Fixed Fix Version/s: cpp-0.1.0 Issue resolved by