[
https://issues.apache.org/jira/browse/OOZIE-1231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13633507#comment-13633507
]
Mohammad Kamrul Islam commented on OOZIE-1231:
----------------------------------------------
Overall I think this is a very confusing and long discussed issue. No single
approach will solve this.
UI: I don't like the option of including another tab for only this. Rather a
new item after "Console URL" in action Info will be better.
Backend :
More confusions are here.
Let's solve the original inconsistency issue.
Robert's comments are better. But it will also break backward-compatibility.
One option to workaround this is:
Whoever will call older version of REST API (such as v1), Oozie will return the
way it is now. For new REST API version (v2+), we will return the newer fields
as <LauncherId, ChildIDs>.
> 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
