hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eugene Koifman (JIRA)" <>
Subject [jira] [Updated] (HIVE-10066) Hive on Tez job submission through WebHCat doesn't ship Tez artifacts
Date Fri, 27 Mar 2015 00:42:52 GMT


Eugene Koifman updated HIVE-10066:
    Attachment: HIVE-10066.2.patch

patch 2 addresses comments from [~thejas]

> Hive on Tez job submission through WebHCat doesn't ship Tez artifacts
> ---------------------------------------------------------------------
>                 Key: HIVE-10066
>                 URL:
>             Project: Hive
>          Issue Type: Bug
>          Components: Tez, WebHCat
>    Affects Versions: 1.0.0
>            Reporter: Eugene Koifman
>            Assignee: Eugene Koifman
>         Attachments: HIVE-10066.2.patch, HIVE-10066.patch
> 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 are needed by any other services’
daemons). It does not have any cluster 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 tarball be uploaded to HDFS and the config has an entry “tez.lib.uris”
which points to the HDFS path. "
> We need a way to pass client jars and tez-site.xml to the LaunchMapper.
> We should create a general purpose mechanism here which can supply additional artifacts
per job type.

This message was sent by Atlassian JIRA

View raw message