Details
-
Type:
Bug
-
Status: Resolved
-
Priority:
Critical
-
Resolution: Fixed
-
Affects Version/s: 3.7.0
-
Fix Version/s: 3.9.0
-
Component/s: con.oozie
-
Labels:None
-
Environment:
EC2 3x m3.xlarge master nodes + 32 x d2.xlarge compute nodes
Ubuntu 12
Reproduced with both Chrome 42 and Firefox 32 on Mac OS 10.9
-
Target Version:
Description
In the version of HUE shipped with CDH5.4.0 (v3.7) there is a significant bug in the new coordinator editor. If you change the scheduling using the editor widget, save the coordinator, then go back to it, HUE has failed to persist the non-default scheduling information. We can also not get it to persist non-default schedules when using the "advanced" button and entering a crontab format schedule.
We see this problem consistently. It occurs both when editing new coordinators and with ones that previously worked but were migrated to the new editor.
The attached screenshots:
before.png – the state of the editor after changing the schedule and saving
after.png – the state of the editor after returning to the coordinator list, then clicking back to the coordinator
