You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@drill.apache.org by "Jason Altekruse (JIRA)" <ji...@apache.org> on 2015/01/27 21:04:34 UTC

[jira] [Commented] (DRILL-2079) Index out of bounds exception while performing external sort

    [ https://issues.apache.org/jira/browse/DRILL-2079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14294094#comment-14294094 ] 

Jason Altekruse commented on DRILL-2079:
----------------------------------------

+1

> Index out of bounds exception while performing external sort
> ------------------------------------------------------------
>
>                 Key: DRILL-2079
>                 URL: https://issues.apache.org/jira/browse/DRILL-2079
>             Project: Apache Drill
>          Issue Type: Bug
>            Reporter: Mehant Baid
>            Assignee: Mehant Baid
>             Fix For: 0.8.0
>
>         Attachments: DRILL-2079.patch
>
>
> With a data set large enough to cause the external sort to spill we hit index out of bounds exception when we have a fixed width vector in the record batch. With the recent automatic memory reallocation fix (DRILL-1960) we moved to allocating memory for fixed width vectors with target record counts (instead of allocateNewSafe). However in PriorityQueueCopierTemplate we still use the old interface and since we don't use copyFromSafe() anymore we hit IOOB since the vector is not sized as expected. Fix is simply to use AllocationHelper so that we allocate the exact memory required by fixed width vectors.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)