Mailing-List: contact issues-help@hive.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hive.apache.org
Date: Thu, 4 Aug 2016 21:15:20 +0000 (UTC)
From: "Sergey Shelukhin (JIRA)" <jira@apache.org>
To: issues@hive.apache.org
Message-ID: <JIRA.12995032.1470344534000.228710.1470345320617@Atlassian.JIRA>
In-Reply-To: <JIRA.12995032.1470344534000@Atlassian.JIRA>
References: <JIRA.12995032.1470344534000@Atlassian.JIRA> <JIRA.12995032.1470344534147@arcas>
Subject: [jira] [Commented] (HIVE-14433) refactor LLAP plan cache avoidance
 and fix issue in merge
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 04 Aug 2016 21:15:22 -0000


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

Sergey Shelukhin commented on HIVE-14433:
-----------------------------------------

[~prasanth_j] fyi

> refactor LLAP plan cache avoidance and fix issue in merge
> ---------------------------------------------------------
>
>                 Key: HIVE-14433
>                 URL: https://issues.apache.org/jira/browse/HIVE-14433
>             Project: Hive
>          Issue Type: Bug
>            Reporter: Sergey Shelukhin
>
> Map and reduce processors do this:
> {noformat}
>     if (LlapProxy.isDaemon()) {
>       cache = new org.apache.hadoop.hive.ql.exec.mr.ObjectCache(); // do not cache plan
> ...
> {noformat}
> but merge processor just gets the plan. If it runs in LLAP, it can get a cached plan. Need to move this logic into ObjectCache itself, via a isPlan arg or something. That will also fix this issue for merge processor


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