Return-Path: X-Original-To: apmail-drill-issues-archive@minotaur.apache.org Delivered-To: apmail-drill-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 1451110380 for ; Wed, 11 Feb 2015 09:05:12 +0000 (UTC) Received: (qmail 72585 invoked by uid 500); 11 Feb 2015 09:05:12 -0000 Delivered-To: apmail-drill-issues-archive@drill.apache.org Received: (qmail 72546 invoked by uid 500); 11 Feb 2015 09:05:12 -0000 Mailing-List: contact issues-help@drill.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@drill.apache.org Delivered-To: mailing list issues@drill.apache.org Received: (qmail 72536 invoked by uid 99); 11 Feb 2015 09:05:12 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 11 Feb 2015 09:05:12 +0000 Date: Wed, 11 Feb 2015 09:05:11 +0000 (UTC) From: "Mehant Baid (JIRA)" To: issues@drill.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (DRILL-2211) Define realloc(), allocationMonitor behavior when using fixed size allocation methods in ValueVectors MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Mehant Baid created DRILL-2211: ---------------------------------- Summary: 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 Reporter: Mehant Baid Assignee: Mehant Baid 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)