You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@drill.apache.org by "Mehant Baid (JIRA)" <ji...@apache.org> on 2015/03/04 03:57:05 UTC

[jira] [Resolved] (DRILL-2211) Define realloc(), allocationMonitor behavior when using fixed size allocation methods in ValueVectors

     [ https://issues.apache.org/jira/browse/DRILL-2211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mehant Baid resolved DRILL-2211.
--------------------------------
    Resolution: Fixed

Fixed in 9c0738d94f246443554a1b6d03c7a8d4d21d29a8

> Define realloc(), allocationMonitor behavior when using fixed size allocation methods in ValueVectors
> -----------------------------------------------------------------------------------------------------
>
>                 Key: DRILL-2211
>                 URL: https://issues.apache.org/jira/browse/DRILL-2211
>             Project: Apache Drill
>          Issue Type: Bug
>          Components: Execution - Data Types
>            Reporter: Mehant Baid
>            Assignee: Mehant Baid
>             Fix For: 0.9.0
>
>
> In our value vectors implementation we have two major schemes to perform allocation. 
> allocateNew(int)  -> Allocate for exact number of records
> allocateNew() -> Allocate based on allocation monitors.
> Currently we don't have a paradigm for when a physical operator wants to exercise allocation using both the above schemes causing a few issues for such operators. 



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