[
https://issues.apache.org/jira/browse/OOZIE-1888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14037036#comment-14037036
]
Shwetha G S commented on OOZIE-1888:
------------------------------------
Since oozie binary package already contains oozie-default.xml(for reference),
why not ship empty oozie-site.xml and let the users add override properties. It
doesn't make any sense to define the same property, same value in both
oozie-default.xml and oozie-site.xml?
If we make sure all configs read in code are all in oozie-default.xml, we
should avoid defining default values in code. The default value in code won't
be used anyway in this case
> 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)
