[
https://issues.apache.org/jira/browse/OOZIE-1160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13551708#comment-13551708
]
Robert Kanter commented on OOZIE-1160:
--------------------------------------
I agree that something more generic would be better. I think some of the other
actions have similar behavior and could include their child job url(s) there.
>From what I figured out when looking at OOZIE-1025, we won't know the child
>job url(s) until the pig job actually finishes; make sure to take this into
>consideration.
> Oozie web-console to display all job URLs spawned by Pig
> --------------------------------------------------------
>
> Key: OOZIE-1160
> URL: https://issues.apache.org/jira/browse/OOZIE-1160
> Project: Oozie
> Issue Type: Improvement
> Reporter: Mona Chitnis
> Assignee: Mona Chitnis
> Original Estimate: 72h
> Remaining Estimate: 72h
>
> The Oozie web UI only displays the console URL of the Pig launcher job. Users
> need access to clickable console URLs of all the spawned 'child' jobs for
> quicker debugging
> To elaborate a bit more on the changes,
> The Workflow action JSON response object returned would now have an
> additional field called e.g. 'pigUrls', which I'm planning in a
> comma-separated string of all the child URLs, and the web console javascript
> code then obtains and splits into clickable fields, dynamically displayed
> based on the quantity. So this is mainly a client-side API change, making use
> of that field.
> Thoughts?
--
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
