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

Posted to dev@drill.apache.org by "Venki Korukanti (JIRA)" <ji...@apache.org> on 2014/05/22 05:10:37 UTC

[jira] [Updated] (DRILL-809) BitVector.allocateNewSafe should check for max of 1 and new allocationValueCount

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

Venki Korukanti updated DRILL-809:
----------------------------------

    Attachment: DRILL-809.1.patch

Attaching patch. It also has changes to reset {{allocationMonitor}} whenever {{allocationValueCount}} is changed.

> BitVector.allocateNewSafe should check for max of 1 and new allocationValueCount
> --------------------------------------------------------------------------------
>
>                 Key: DRILL-809
>                 URL: https://issues.apache.org/jira/browse/DRILL-809
>             Project: Apache Drill
>          Issue Type: Bug
>            Reporter: Venki Korukanti
>            Assignee: Venki Korukanti
>         Attachments: DRILL-809.1.patch
>
>
> {code}
> allocationValueCount = Math.min(1, (int)(allocationValueCount * 0.9));
> {code}
> This will cause no memory allocated and all subsequent setSafe calls fail.



--
This message was sent by Atlassian JIRA
(v6.2#6252)