[
https://issues.apache.org/jira/browse/IMPALA-12348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17863914#comment-17863914
]
Saulius Valatka commented on IMPALA-12348:
------------------------------------------
This seems to no longer happen in 4.4.0. Skimming through the changelog it's
very non-obvious to me what fixed it.
> Segfault when selecting >500 columns with a filter
> --------------------------------------------------
>
> Key: IMPALA-12348
> URL: https://issues.apache.org/jira/browse/IMPALA-12348
> Project: IMPALA
> Issue Type: Bug
> Components: be
> Affects Versions: Impala 4.2.0
> Reporter: Saulius Valatka
> Priority: Major
> Attachments: 89da31ae-cc29-4394-e8c984a6-f9d9eeb3.dmp, gdb.txt,
> part-00000-50adce0a-aaff-4030-9f9e-9c2093562f87.c000.snappy.parquet
>
>
> Impala daemon consistently crashes with a segfault when selecting a few
> hundred columns with a filter from a Parquet based table, i.e.: a query like:
> {{select x1, x2, ..., x500 from table where x1 = 'value' limit 100}}
> It doesn't seem to matter what columns are selected/filtered, as long as a
> certain threshold is reached. Interestingly it does not crash without the
> filter. Same queries did not crash with Impala 3.2.0.
> Attached a gdb backtrace from a debug build. Also attached a minidump, but I
> see it's only showing ?? backtraces for some reason.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
