[
https://issues.apache.org/jira/browse/OOZIE-2060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14303341#comment-14303341
]
Ben Roling commented on OOZIE-2060:
-----------------------------------
Thanks for the feedback guys. I removed the system property reference because
my feeling was its presence implied that it should not be considered safe to
have a dependency on the actual filename. If that is the case, then a
consumer should not feel safe using the {{-conf}} method. If the filename were
to change in a future release, anyone using {{-conf}} would need to change
their workflow.xml.
Your comment suggests to me you want to preserve the right to change the
filename -- should I just drop the {{-conf}} mention entirely or leave it in
and note that using it is risks being broken in a future release?
My feeling was that it is unlikely you will need/want to change the filename
anyway but your opinion may vary.
> Incorrect documentation of Java action config XML filename
> ----------------------------------------------------------
>
> Key: OOZIE-2060
> URL: https://issues.apache.org/jira/browse/OOZIE-2060
> Project: Oozie
> Issue Type: Sub-task
> Components: docs
> Affects Versions: 3.3.2, 4.0.0, 4.0.1
> Reporter: Ben Roling
> Priority: Minor
> Attachments: OOZIE-2060.patch, OOZIE-2060.patch
>
>
> The [documentation of Java
> action|https://oozie.apache.org/docs/4.0.1/WorkflowFunctionalSpec.html#a3.2.7_Java_Action]
> suggests that Java action configuration is available in a file named
> "oozie-action.conf.xml".
> This does not seem to me to be true. My experience is that this
> configuration is available in "action.xml".
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
