You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@drill.apache.org by "Pritesh Maker (JIRA)" <ji...@apache.org> on 2019/01/30 22:35:00 UTC
[jira] [Updated] (DRILL-7018) Drill Query (when
store.parquet.reader.int96_as_timestamp=true) on Parquet File fails with
Error: SYSTEM ERROR: IndexOutOfBoundsException: readerIndex: 0,
writerIndex: 372 (expected: 0 <= readerIndex <= writerIndex <=
capacity(256))
[ https://issues.apache.org/jira/browse/DRILL-7018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pritesh Maker updated DRILL-7018:
---------------------------------
Remaining Estimate: 0h (was: 24h)
Original Estimate: 0h (was: 24h)
Reviewer: Boaz Ben-Zvi
> Drill Query (when store.parquet.reader.int96_as_timestamp=true) on Parquet File fails with Error: SYSTEM ERROR: IndexOutOfBoundsException: readerIndex: 0, writerIndex: 372 (expected: 0 <= readerIndex <= writerIndex <= capacity(256))
> ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DRILL-7018
> URL: https://issues.apache.org/jira/browse/DRILL-7018
> Project: Apache Drill
> Issue Type: Improvement
> Components: Storage - Parquet
> Affects Versions: 1.14.0
> Reporter: salim achouche
> Assignee: salim achouche
> Priority: Major
> Fix For: 1.16.0
>
> Original Estimate: 0h
> Remaining Estimate: 0h
>
> alter system set `store.parquet.reader.int96_as_timestamp`= true
> run query witch projects a column of type Parquet INT96 timestamp with 31 nulls
> The following exception will be thrown:
> java.lang.IndexOutOfBoundsException: readerIndex: 0, writerIndex: 372 (expected: 0 <= readerIndex <= writerIndex <= capacity(256))
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)