[
https://issues.apache.org/jira/browse/OOZIE-2814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16349221#comment-16349221
]
Attila Sasvari commented on OOZIE-2814:
---------------------------------------
[~rkanter] thanks a lot. I changed the java-main example workflow to use
{{resource-manager}} instead of {{job-tracker}}
{code:java}
<workflow-app xmlns="uri:oozie:workflow:1.0" name="java-main-wf">
<start to="java-node"/>
<action name="java-node">
<java>
<resource-manager>${jobTracker}</resource-manager>{code}
Result of job submission:
{code:java}
Error: E0701 : E0701: XML schema error, No job-tracker defined{code}
Workflow can be validated against the schema just fine, but
{{LiteWorkflowAppParser}} needs to be adjusted as it only tries to fetch the
child of the {{job-tracker}} element:
https://github.com/apache/oozie/blob/ef6d0af5edeb18fbc0259d1962ac70f8ad7c2a0c/core/src/main/java/org/apache/oozie/workflow/lite/LiteWorkflowAppParser.java#L424
TestLiteWorkflowAppParser is to be extended too.
> OYA: Update example workflows to newest schemas
> -----------------------------------------------
>
> Key: OOZIE-2814
> URL: https://issues.apache.org/jira/browse/OOZIE-2814
> Project: Oozie
> Issue Type: Sub-task
> Affects Versions: 5.0.0
> Reporter: Robert Kanter
> Assignee: Attila Sasvari
> Priority: Blocker
> Attachments: OOZIE-2814-00.patch
>
>
> OOZIE-2687 will add in a whole set of newer schemas that are more
> Yarn-centric. Most, if not all, examples currently use pretty old versions
> of the schemas. We should take this opportunity to update the examples to
> the newest schemas added by OOZIE-2687, which should help demonstrate them.
> It may make sense to keep the older schemas too, to show that older workflows
> still work. We have some examples where we have two workflow XML files that
> do the same thing in different ways.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
