Support Questions

Find answers, ask questions, and share your expertise
Announcements
Celebrating as our community reaches 100,000 members! Thank you!

Oozie coordinator editor - problems with using datasets.

avatar
Contributor

Hue 2.3.0 is the version I am using.  I tried to scan the list of fixes in Hue 2.4.0 but no luck. 

 

I am trying create an oozie coordinator which has date as output.  I see a list of datasets I previously created when in "Step 4: output - SHOWING EXISTING".  So I added one like

 

    name:dateYYYYMMDD  dataset: DT    which should uri as ${YEAR}${MONTH}${DAY}

 

and saved coordinator.  

 

Strange thing is that although I see "dateYYYYMMDD -> DT" as output.  I DON'T see PATH for it.  I still seesthe message "There are currently no defined outputs.". 

 

If I try to submit now, a box popup asking me to fill in "dateYYYYMMDD". But that is DT and is defined. 

 

If I went off to another tab say: work flow editor and come back to this coordinator, Step 4: output shows empty.  It seems the output was never added in the first place. 

 

Another problem which is minor is that in SHOW EXISTING DATASET, the delete does not work for me.  I can delete some datasets and save coordinator, go to another tab (Workflows), come back to list existing datasets, they are still there. 

 

To sum up, I have faced with 3 problems: 

1  adding/deleting input/output dataset does not stick.  It seems "save coordinator" did not update the databse properly.

2. input/output datasets don't have PATH shown (The sample output REDUCER_SLEEP_TIME) shows PATH. So I think the PATH is expected to show. 

3. "delete" action on show existing datasets does not stick. The deletion can't be saved.

 

Anyone experiencing these problems?  I am bit suprised that I would not find much hits when googling these problems.  Is this because Hue 2.3.0 or not enough people adapted to Hue for oozie scheduling?  Is there better GUI alternatives?

 

Please let me know if these problems do have fixes in Hue 2.4.0.  GUI is nice to use and easy for other to see, but I am starting to thinking I am only one of a few who is using this. Perhaps I should wait for a future release.

 

 

Thanks.

1 ACCEPTED SOLUTION

avatar
Contributor

It seems Hue 2.5.0 has fixed the problem.  Chrome works the same as FireFox. 

View solution in original post

14 REPLIES 14

avatar
Super Guru

Nice!

 

Can you share your Chrome and Firefox version that way we can investigate this?

avatar
Contributor

Chrome: Version 28.0.1500.71

Firefox: Version 22.0

 

Both running on Ubuntu 12.04

 

avatar
Contributor

I upgrade to the latest google Chrome Version 29.0.1547.62

 

Unfortunately, this version of Chrome is still not working for me on Ubunt 12.04

avatar
Contributor

It seems Hue 2.5.0 has fixed the problem.  Chrome works the same as FireFox. 

avatar
Super Guru

Awesome and thanks for the feedback!