[
https://issues.apache.org/jira/browse/OOZIE-2718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15856515#comment-15856515
]
Xiaobin Zheng commented on OOZIE-2718:
--------------------------------------
Thx for taking a look [~gezapeti]!
There are already test cases covering dryrun:
TestBundleSubmitXCommand.testJobXmlCommentRemoved and
TestBundleSubmitXCommand.testDuplicateCoordName. Both of them are using 'new
BundleSubmitXCommand(true, jobConf)' to run as 'dryrun'. Since you asked, I
added one more assertion in 'testJobXmlCommentRemoved' in patch-3 for dryrun
test case to be more clear.
> Improve -dryrun for bundles
> ---------------------------
>
> Key: OOZIE-2718
> URL: https://issues.apache.org/jira/browse/OOZIE-2718
> Project: Oozie
> Issue Type: Bug
> Reporter: Peter Cseh
> Assignee: Xiaobin Zheng
> Attachments: OOZIE-2718-1.patch, OOZIE-2718-2.patch,
> OOZIE-2718-3.patch
>
>
> When trying to do a -dryrun for Oozie:
> {code}
> error:
> Error: E1310 : E1310: Bundle Job submission Error: [null]
> {code}
> The
> [documentation|https://oozie.apache.org/docs/4.2.0/DG_CommandLineTool.html#Dryrun_of_Coordinator_Job]
> states that dryruns are working for workflows and coordinators.
> {quote}
> "Dryrun a workflow (since 3.3.2) or coordinator (since 2.0) job without
> actually executing it"
> {quote}
> The easy fix is to document that it does not work and create an appropriate
> error message for it. It's also possible to add support for bundle dryruns.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
