[
https://issues.apache.org/jira/browse/OOZIE-120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hadoop QA resolved OOZIE-120.
-----------------------------
Resolution: Fixed
> GH-85: Oozie coordinator UI enhancement.
> ----------------------------------------
>
> Key: OOZIE-120
> URL: https://issues.apache.org/jira/browse/OOZIE-120
> Project: Oozie
> Issue Type: Bug
> Reporter: Hadoop QA
>
> The current UI implementation for oozie-coordinator lacks some basis
> usability feature. After submitting a coordinator application, one cannot see
> the coordinator application log. One has to use the command line option to
> obtain the logs.
> The same holds true for the coordinator jobs that get started at
> designated frequency. If the job is waiting or inany other state, one has
> again take the command line path to obtain any info for the same.
> Once we go live using oozie coordinator as croning/triggering component I
> am pretty sure the SE&O team will need these interfaces to easily access for
> monitoring and first hand analysis of any situation. For dev also its a
> required feature.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
