[
https://issues.apache.org/jira/browse/PARQUET-995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16019758#comment-16019758
]
Xianjin YE commented on PARQUET-995:
------------------------------------
Hi, [~wesmckinn] how is this issue found?
I was haunted by this bug all day today. In our application, the segfault
showed up in the core dump pointed to some innocent code(not related to
parquet) due to the bad memory access. I tried everything and until I found
this issue, it occurred to me this might be the root cause. And indeed the
problem is solved when I merged the latest parquet code.
> [C++] Int96 reader in parquet_arrow uses size of Int96Type instead of Int96
> ---------------------------------------------------------------------------
>
> Key: PARQUET-995
> URL: https://issues.apache.org/jira/browse/PARQUET-995
> Project: Parquet
> Issue Type: Bug
> Components: parquet-cpp
> Reporter: Wes McKinney
> Assignee: Wes McKinney
> Priority: Blocker
> Fix For: cpp-1.1.0
>
>
> This produces a segfault when reading {{alltypes_plain.parquet}} with
> parquet::arrow. I will see if I can reproduce with a test case.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
