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

["Hanifi Gunes (JIRA)" <ji...@apache.org>]

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

Hanifi Gunes edited comment on DRILL-2211 at 3/2/15 9:36 PM:
-------------------------------------------------------------

[~mehant] as discussed last week, could you verify if DRILL-2178 fixes this and close the issue? thx


was (Author: hgunes):
[~mehant] as discusses last week, could you verify if DRILL-2178 fixes this and close the issue? thx

> 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)