[
https://issues.apache.org/jira/browse/OOZIE-1231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13638699#comment-13638699
]
Ryota Egashira commented on OOZIE-1231:
---------------------------------------
Thanks a lot, Robert and Mohammad for feedback.
after internal discussion, here is our plan.
Backend >
go with Robert's "most correct" solution, meaning
launcher ID -->external ID, console URL
spawned child job ID --> external_child_ids
Console UI >
pig action/hive action already use different tab "child Job URLs" (OOZIE-1160),
so map-reduce action follow the same to make it consistent.
(attaching new screenshot, please ignore previous version, which is not valid)
but not to confuse existing users, changed label name from "Console URL" to
"Launcher Console URL" on "Action Info" tab to emphasize it is launcherID.
API >
if some users using curl command to hit API for externalID of map-reduce, the
change we are discussing here breaks backward-compatibility
follow Mohammad's suggestion to maintain API backward comparability
v1 api returns back the same as before, (i.e., in returned JSON,
externalID/consoleURL->spawned child ID, external_child_ids-> null). but since
ID swap doesn't happened anymore in backend, I changed internal code of
V1JobServlet a bit for API to keep returning the same result.
v1.1 api returns externalID/ConsoleUrl --> launcher ID, externalChildIDs -->
spawned child JobID.
(we made new version to v1.1, since this change is only for workflow action
part, but not fully sure what is right naming convention..)
oozie-console.js was using v1, but changed portion of fetching workflow action
to use v1.1.
DataBase >
no DB scheme change required, but for old wf action records remaining in DB,
upgrade option (OozieDBCLI) need to be changed to do replace external_child_ids
with external_id (spawned child job). old wf action already lost launcher ID,
so we cannot populate externalID/consoleURL properly anyway. end up showing
"n/a" in UI.
Please let me know if anything missing here.
> 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
