[
https://issues.apache.org/jira/browse/OOZIE-1231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13632247#comment-13632247
]
Robert Kanter commented on OOZIE-1231:
--------------------------------------
Won't option 2 possibly break user code or other clients (i.e. not the Oozie
CLI client) that use the API to get the consoleURL or externalID? They'll be
expecting a single value but will instead get two values separated by
something.
I'd say that the "most correct" solution to this is that the
consoleURL/externalID should have the launcher job (to be consistent with the
other action types) and the MR job should be listed somewhere else
(external_child_ids?). And I'd argue that the MR action having behavior
inconsistent with the other actions is more confusing.
Would it make sense to have the consoleURL/externalID be the launcher job and
put the MR job in external_child_ids? I know that's changing the existing
behavior for the MR action, but if we do it for 4.0, maybe that's okay (plus,
it would be consistent with the other actions)?
> Provide access to launcher job URL from web console when using Map Reduce
> action
> --------------------------------------------------------------------------------
>
> Key: OOZIE-1231
> URL: https://issues.apache.org/jira/browse/OOZIE-1231
> Project: Oozie
> Issue Type: Bug
> Affects Versions: trunk
> Reporter: Ryota Egashira
> Assignee: Ryota Egashira
> Labels: oozie
> Attachments: Screen Shot Launcher_Job_URL_tab.png
>
>
> there are applications where custom inputformat used in MR action, and log
> message from the inputformat is written on launcher task log. for debugging
> purpose, users need to check the launcher task log. but currently in MR
> action, oozie automatically swaps external ID, and do not expose the launcher
> ID in web-console. (now only way is to to grep oozie.log). this jira is to
> show launcher job URL on web console when using Map Reduce action
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
