[
https://issues.apache.org/jira/browse/OOZIE-1231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13631583#comment-13631583
]
Ryota Egashira commented on OOZIE-1231:
---------------------------------------
here are couple of design discussions.
UI Change>
MapReduce Action automatically swap launcher job ID to spawned job ID. Oozie UI
displays spawned job as console URL on "Action Info" Tab.
its has been like this so far, and changing console URL to show launcher Job
will confuse existing users. Thus, we think it might be better to add new tab
"launcher job URL" in action detail popup of map-reduce action, while leaving
existing console URL as it is. please see attached screen shot.
Backend change>
launcher job ID need to be persisted on DB to later display it on UI, and issue
is which column to store it. couple of candidates.
1) external_child_ids
this column currently unused for map-reduce action, and straightforward to use
it. flip side is that launcher ID is not "child_ids" and syntax becomes
irrelevant.
2) consoleURL / externalID
append launcher job ID to consoleURL/externalID column which currently keeps
spawned Job ID, using some separator.
from syntax perspective, might be better than option 1)
flip side is that it needs minor change in oozie-console.js to do additional
string processing to separate them before showing it on UI. also backend side
needs minor change to append the info. but possible to keep backward
compatibility.
3) add new column
it is clean but schema change required, and a bit overkill just to store
launcher job ID of map-reduce action.
currently I am inclined to 2) option, any feedback appreciated.
> 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
