Mailing-List: contact dev-help@hive.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hive.apache.org
Date: Tue, 13 Jan 2015 04:12:34 +0000 (UTC)
From: "Xuefu Zhang (JIRA)" <jira@apache.org>
To: hive-dev@hadoop.apache.org
Message-ID: <JIRA.12763028.1419032737000.67212.1421122354978@Atlassian.JIRA>
In-Reply-To: <JIRA.12763028.1419032737000@Atlassian.JIRA>
References: <JIRA.12763028.1419032737000@Atlassian.JIRA>
 <JIRA.12763028.1419032737394@arcas>
Subject: [jira] [Commented] (HIVE-9178) Create a separate API for remote
 Spark Context RPC other than job submission [Spark Branch]
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Xuefu Zhang commented on HIVE-9178:
-----------------------------------

The patch looks good to me. [~chengxiang li], could you also take a look.

[~brocknoland], I'm wondering why the test hasn't kicked in for this.

> Create a separate API for remote Spark Context RPC other than job submission [Spark Branch]
> -------------------------------------------------------------------------------------------
>
>                 Key: HIVE-9178
>                 URL: https://issues.apache.org/jira/browse/HIVE-9178
>             Project: Hive
>          Issue Type: Sub-task
>          Components: Spark
>            Reporter: Xuefu Zhang
>            Assignee: Marcelo Vanzin
>         Attachments: HIVE-9178.1-spark.patch
>
>
> Based on discussions in HIVE-8972, it seems making sense to create a separate API for RPCs, such as addJar and getExecutorCounter. These jobs are different from a query submission in that they don't need to be queued in the backend and can be executed right away.


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