[
https://issues.apache.org/jira/browse/OOZIE-1888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14036986#comment-14036986
]
Robert Kanter commented on OOZIE-1888:
--------------------------------------
I think the idea is that all properties should go into oozie-default and the
common ones, or ones that don't have a "good" default, go in oozie-site to make
it easy for the user to change them. I think the sharelib location property is
a common one that should stay in oozie-site.
Though it is unfortunate that we don't have a way of keeping oozie-default,
oozie-site and the defaults in the code (i.e. when you do {{conf.get(PROP_NAME,
DEFAULT_VALUE)}}) in sync automatically. We've had a few problems with this
before.
> oozie.service.WorkflowAppService.system.libpath is wrong in oozie-default.xml
> -----------------------------------------------------------------------------
>
> Key: OOZIE-1888
> URL: https://issues.apache.org/jira/browse/OOZIE-1888
> Project: Oozie
> Issue Type: Bug
> Components: core
> Affects Versions: trunk
> Reporter: Robert Kanter
> Assignee: Robert Kanter
> Priority: Critical
> Attachments: OOZIE-1888.patch
>
>
> The current value of {{oozie.service.WorkflowAppService.system.libpath}} in
> oozie-default is "hdfs:///user/$\{user.name\}/share/lib". This is a problem
> for three reasons:
> # It assumes HDFS (what about viewfs?)
> # It won't actually work because it's missing a host:port
> # It doesn't match the default oozie-site.xml, which has
> "/user/$\{user.name\}/share/lib"
> We should change it to "/user/$\{user.name\}/share/lib" as this works on both
> HDFS and viewfs and matches oozie-site.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
