[
https://issues.apache.org/jira/browse/DRILL-6570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16528968#comment-16528968
]
ASF GitHub Bot commented on DRILL-6570:
---------------------------------------
sachouche commented on issue #1354: DRILL-6570: Fixed IndexOutofBoundException
in Parquet Reader
URL: https://github.com/apache/drill/pull/1354#issuecomment-401579979
The reason I didn't remove the ColumnPrecisionInfo.precision is that I am
allowing myself another chance, in the future, to optimize the fixed length
path; at this time, the savings are very less (about 2kb). Though, I can remove
this input object if it helps code clarity.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> IndexOutOfBoundsException when using Flat Parquet Reader
> ---------------------------------------------------------
>
> Key: DRILL-6570
> URL: https://issues.apache.org/jira/browse/DRILL-6570
> Project: Apache Drill
> Issue Type: Bug
> Components: Storage - Parquet
> Reporter: salim achouche
> Assignee: salim achouche
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.14.0
>
> Original Estimate: 2h
> Remaining Estimate: 2h
>
> * The Parquet Reader creates a reusable bulk entry based on the column
> precision
> * It uses the column precision for optimizing the intermediary heap buffers
> * It first detected the column was fixed length but then it reverted this
> assumption when the column changed precision
> * This step was fine except the bulk entry memory requirement changed though
> the code didn't update the bulk entry intermediary buffers
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
