You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Adriano (JIRA)" <ji...@apache.org> on 2016/05/04 08:51:12 UTC

[jira] [Created] (OOZIE-2523) Enable Oozie to lad the jar(s) class of hive.aux.jars.path (when it is specified in the hive-site.xml and it is attached to the workflow)

Adriano created OOZIE-2523:
------------------------------

             Summary: Enable Oozie to lad the jar(s) class of hive.aux.jars.path (when it is specified in the hive-site.xml and it is attached to the workflow)
                 Key: OOZIE-2523
                 URL: https://issues.apache.org/jira/browse/OOZIE-2523
             Project: Oozie
          Issue Type: Improvement
          Components: action, scripts
            Reporter: Adriano


The present Jira is to be intened as implementation request.

Description: Actually Oozie doesn't take in consideration the parameter hive.aux.jars.path (when it is specified in the hive-site.xml).
the value of this parameter is a list of jar class that can be used to interact with HBASE as example.

Request: oozie need to be able to load the jar(s) class listed in hive.aux.jars.path if it is specified in hive-site.xml (that basically is attached to the workflow when it is needed).

Advantage: Better integration between HBASE>HIVE>OOZIE>HUE: In case there are many jar(s) the user doesn't need to remember to add it to every workflow. If it is already set hive.aux.jars.path at hive service level and it will be read by oozie and the class will be loaded and this mechanism will simple works. It will save space considering that the jar(s) doesn't need to be copied on each workflow.



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