[ https://issues.apache.org/jira/browse/OOZIE-2439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15099223#comment-15099223 ]
Robert Kanter commented on OOZIE-2439: -------------------------------------- The tricky thing here is that we can't make {{FsActionExecutor}} set {{requiresNameNodeJobTracker()}} to {{true}} because # the NN is actually optional for the FS Action (as long as you specify it for each path) # The JT isn't even optional (the XSD doesn't allow it) So we can't simply set it to {{true}} or it would have other side effects. I don't think we should change the semantics of {{requiresNameNodeJobTracker()}} at this point either. We'll have to do something custom, similar to what was done in OOZIE-2030 for the SubWorkflow Action. > FS Action no longer uses name-node > ---------------------------------- > > Key: OOZIE-2439 > URL: https://issues.apache.org/jira/browse/OOZIE-2439 > Project: Oozie > Issue Type: Bug > Affects Versions: trunk > Reporter: Robert Kanter > Assignee: Robert Kanter > Priority: Blocker > Fix For: trunk > > > As reported by [~olch...@gmail.com] in [this > comment|https://issues.apache.org/jira/browse/OOZIE-2187?focusedCommentId=15099135&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15099135] > of OOZIE-2187, the FS Action no longer uses the {{<name-node>}} in either > the action itself, the global section, or the default NN in oozie-site. > This is a regression. -- This message was sent by Atlassian JIRA (v6.3.4#6332)