That was my pet peeve for a long time, it'd be a welcome change to replace jobTracker nomenclature.
On Jan 31, 2018 4:05 PM, "Robert Kanter (JIRA)" <[email protected]> wrote: > > [ https://issues.apache.org/jira/browse/OOZIE-2814?page= > com.atlassian.jira.plugin.system.issuetabpanels:comment- > tabpanel&focusedCommentId=16347605#comment-16347605 ] > > Robert Kanter commented on OOZIE-2814: > -------------------------------------- > > I think we should also update {{<job-tracker>}} to {{<resource-manager>}} > to encourage users to start using it. > > > 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) >
