Return-Path: X-Original-To: apmail-hive-dev-archive@www.apache.org Delivered-To: apmail-hive-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 67687102EC for ; Tue, 24 Mar 2015 01:25:53 +0000 (UTC) Received: (qmail 77672 invoked by uid 500); 24 Mar 2015 01:25:53 -0000 Delivered-To: apmail-hive-dev-archive@hive.apache.org Received: (qmail 77613 invoked by uid 500); 24 Mar 2015 01:25:52 -0000 Mailing-List: contact dev-help@hive.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hive.apache.org Delivered-To: mailing list dev@hive.apache.org Received: (qmail 77602 invoked by uid 99); 24 Mar 2015 01:25:52 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 24 Mar 2015 01:25:52 +0000 Date: Tue, 24 Mar 2015 01:25:52 +0000 (UTC) From: "Eugene Koifman (JIRA)" To: dev@hive.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (HIVE-10066) Hive on Tez job submission through WebHCat doesn't ship Tez artifacts MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Eugene Koifman created HIVE-10066: ------------------------------------- Summary: Hive on Tez job submission through WebHCat doesn't sh= ip Tez artifacts Key: HIVE-10066 URL: https://issues.apache.org/jira/browse/HIVE-10066 Project: Hive Issue Type: Bug Affects Versions: 1.0.0 Reporter: Eugene Koifman Assignee: Eugene Koifman >From [~hitesh]: Tez is a client-side only component ( no daemons, etc ) and therefore it is= meant to be installed on the gateway box ( or where its client libraries a= re needed by any other services=E2=80=99 daemons). It does not have any clu= ster dependencies both in terms of libraries/jars as well as configs. When = it runs on a worker node, everything was pre-packaged and made available to= the worker node via the distributed cache via the client code. Hence, its = client-side configs are also only needed on the same (client) node as where= it is installed. The only other install step needed is to have the tez tar= ball be uploaded to HDFS and the config has an entry =E2=80=9Ctez.lib.uris= =E2=80=9D which points to the HDFS path.=20 We need a way to pass client jars and tez-site.xml to the LaunchMapper. We should create a general purpose mechanism here which would also include = sending hive-site.xml to LaunchMapper so that there is no duplication betwe= en hive-site.xml and templeton.hive.properties in webhcat-site.xml. -- This message was sent by Atlassian JIRA (v6.3.4#6332)