Mailing-List: contact dev-help@hive.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hive.apache.org
Date: Fri, 15 Jul 2016 18:01:20 +0000 (UTC)
From: "Eugene Koifman (JIRA)" <jira@apache.org>
To: dev@hive.apache.org
Message-ID: <JIRA.12989874.1468605626000.44097.1468605680622@Atlassian.JIRA>
In-Reply-To: <JIRA.12989874.1468605626000@Atlassian.JIRA>
References: <JIRA.12989874.1468605626000@Atlassian.JIRA> <JIRA.12989874.1468605626046@arcas>
Subject: [jira] [Created] (HIVE-14250) Move FetchTask.initialize() in Driver
 from compile() to execute()
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Fri, 15 Jul 2016 18:01:22 -0000

Eugene Koifman created HIVE-14250:
-------------------------------------

             Summary: Move FetchTask.initialize() in Driver from compile() to execute()
                 Key: HIVE-14250
                 URL: https://issues.apache.org/jira/browse/HIVE-14250
             Project: Hive
          Issue Type: Bug
          Components: Query Planning, Query Processor
    Affects Versions: 2.1.0, 1.3.0
            Reporter: Eugene Koifman


Driver.compile(String command, boolean resetTaskIds) has

      // initialize FetchTask right here
      if (plan.getFetchTask() != null) {
        plan.getFetchTask().initialize(queryState, plan, null, ctx.getOpContext());
      }

It's not clear what the advantage of doing this in compile() vs execute()/runInternal() is.  One of the issues this causes is HIVE-14241.  HIVE-14241 has workaround but a much better fix is to move initialize() to where it should be.
see https://issues.apache.org/jira/browse/HIVE-14241?focusedCommentId=15379774&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15379774


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