You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@arrow.apache.org by "Neal Richardson (JIRA)" <ji...@apache.org> on 2019/07/17 14:43:00 UTC
[jira] [Commented] (ARROW-5965) [Python] Regression: segfault when
reading hive table with v0.14
[ https://issues.apache.org/jira/browse/ARROW-5965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16887119#comment-16887119 ]
Neal Richardson commented on ARROW-5965:
----------------------------------------
Thanks for the report. A few questions:
# Is this reproducible if you try again with the same file? (I wonder if "Killed" means OOM and not segfault)
# Could you provide a (preferably as small as possible) Parquet file that triggers this behavior? I think we'll need that in order to identify and fix any issues.
> [Python] Regression: segfault when reading hive table with v0.14
> ----------------------------------------------------------------
>
> Key: ARROW-5965
> URL: https://issues.apache.org/jira/browse/ARROW-5965
> Project: Apache Arrow
> Issue Type: Bug
> Components: Python
> Affects Versions: 0.14.0
> Reporter: H. Vetinari
> Priority: Critical
> Labels: parquet
>
> I'm working with pyarrow on a cloudera cluster (CDH 6.1.1), with pyarrow installed in a conda env.
> The data I'm reading is a hive(-registered) table written as parquet, and with v0.13, reading this table (that is partitioned) does not cause any issues.
> The code that worked before and now crashes with v0.14 is simply:
> ```
> import pyarrow.parquet as pq
> pq.ParquetDataset('hdfs:///data/raw/source/table').read()
> ```
> Since it completely crashes my notebook (resp. my REPL ends with "Killed"), I cannot report much more, but this is a pretty severe usability restriction. So far the solution is to enforce `pyarrow<0.14`
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)