Mailing-List: contact issues-help@drill.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@drill.apache.org
Date: Mon, 3 Aug 2015 22:57:06 +0000 (UTC)
From: "Chris Westin (JIRA)" <jira@apache.org>
To: issues@drill.apache.org
Message-ID: <JIRA.12851198.1438632752000.361254.1438642626116@Atlassian.JIRA>
In-Reply-To: <JIRA.12851198.1438632752000@Atlassian.JIRA>
References: <JIRA.12851198.1438632752000@Atlassian.JIRA>
 <JIRA.12851198.1438632752967@arcas>
Subject: [jira] [Updated] (DRILL-3594) RuleSets capture and illegally use
 allocator from the first query executed on the drillbit
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Chris Westin updated DRILL-3594:
--------------------------------
    Assignee: Mehant Baid  (was: Chris Westin)

> RuleSets capture and illegally use allocator from the first query executed on the drillbit
> ------------------------------------------------------------------------------------------
>
>                 Key: DRILL-3594
>                 URL: https://issues.apache.org/jira/browse/DRILL-3594
>             Project: Apache Drill
>          Issue Type: Bug
>          Components: Execution - Flow
>    Affects Versions: 1.1.0
>            Reporter: Chris Westin
>            Assignee: Mehant Baid
>
> DrillRuleSets.java lazily creates a list of rules that are used to decide on optimizations. This is done lazily because some of the rules require some context to operate on. However, the ones that do capture context that should not be used after the current query completes. In particular, the new allocator has caught later queries using the allocator created (and since closed) for the first query executed on the drillbit.


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