[jira] [Commented] (PARQUET-1482) [C++] Unable to read data from parquet file generated with parquetjs

["Tera G (JIRA)" <ji...@apache.org>]

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

Tera G commented on PARQUET-1482:
---------------------------------

Hi Everyone,

I see that this fix has been made in arrow's record reader (record_reader.cc). I am using the parquet's low-level API to pull the data from the parquet file in my application.

I am facing the exact problem fixed by this Jira while using the Parquet's low level API.(column_reader.cc).  

As the current fix is not ported to the low level parquet api, I wanted to know if there are any plans to ship these changes to the low-level-api ? 

Also, [~rdmello], can I simply port the fixes you have made in the parquet low-level api ? Will this work ? 

We are using low-level api as it offers more power to us in terms of predicate push down, filtering and skipping of data.

Finally, Is the Open source community's push is to advise developers to use arrow's parquet api or the low level parquet api to access the parquet data ? 

Thank you in advance for your response. 

> [C++] Unable to read data from parquet file generated with parquetjs
> --------------------------------------------------------------------
>
>                 Key: PARQUET-1482
>                 URL: https://issues.apache.org/jira/browse/PARQUET-1482
>             Project: Parquet
>          Issue Type: Bug
>          Components: parquet-cpp
>            Reporter: Hatem Helal
>            Assignee: Rylan Dmello
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: cpp-1.6.0
>
>         Attachments: feeds1kMicros.parquet
>
>          Time Spent: 3.5h
>  Remaining Estimate: 0h
>
> See attached file, when I debug:
> {{% ./parquet-reader feed1kMicros.parquet}}
> I see that the {{scanner->HasNext()}} always returns false.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)