You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Robert Kanter (JIRA)" <ji...@apache.org> on 2015/07/09 00:35:05 UTC

[jira] [Commented] (OOZIE-1724) Make it easier to specify the HCat hive-site.xml for the Oozie Server

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

Robert Kanter commented on OOZIE-1724:
--------------------------------------

I forgot to create the followup JIRA to allow for multiple hive-site.xml files.  

OOZIE-2298

> Make it easier to specify the HCat hive-site.xml for the Oozie Server
> ---------------------------------------------------------------------
>
>                 Key: OOZIE-1724
>                 URL: https://issues.apache.org/jira/browse/OOZIE-1724
>             Project: Oozie
>          Issue Type: Improvement
>    Affects Versions: 4.0.0
>            Reporter: Robert Kanter
>            Assignee: Robert Kanter
>             Fix For: 4.1.0
>
>         Attachments: OOZIE-1724.patch, OOZIE-1724.patch, OOZIE-1724.patch, OOZIE-1724.patch
>
>
> Currently, to specify the hive-site.xml to configure Oozie to talk to the HCatalog server (see http://oozie.apache.org/docs/4.0.0/AG_Install.html#HCatalog_Configuration) it requires you to put the hive-site.xml in the classpath, which means you'd put it in the libext and run the oozie-setup.sh.  
> It would be much easier if we added an oozie-site.xml config property to specify this file, similar to how we specify the core/mapred/yarn/etc-site files for Hadoop (see http://oozie.apache.org/docs/4.0.0/AG_HadoopConfiguration.html).
> Something like:
> {code:xml}
> <property>
>      <name>oozie.service.HCatAccessorService.hcat.configuration</name>
>      <value>path/to/hive-site.xml</value>
> </property>
> {code}



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