You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 6, 2018. It is now read-only.
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.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
The text was updated successfully, but these errors were encountered: