Member since
10-19-2014
58
Posts
6
Kudos Received
2
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
5807 | 03-20-2016 10:41 PM | |
10672 | 04-26-2015 02:30 AM |
04-01-2015
11:09 PM
Thanks Romain!
... View more
03-30-2015
10:21 PM
Thanks for the update Romain. When is Hue 4 targeted for?
... View more
03-30-2015
11:08 AM
So is it in RAM or some other temp directory? How can I prevent a Hue service crash from wiping out the workflow which has been edited but not yet persisted in the workspace directory?
... View more
03-30-2015
08:54 AM
To follow up: the behaviour I observed is that after the scheduled execution through coordinator, the new actions were shown in the Workflows dashboard Graph tab, however they were skipped during the execution run. See attached screenshot. The new actions introduced were the fork "RunThingsInParallel" and the two actions (both Hive) in the right hand side branch. They are all greyed out rather than the green OK status during and after the execution, which was successful. I will be raising a support call for this.
... View more
03-30-2015
08:24 AM
1 Kudo
Hi Romain, thanks for your answer. I completely get your point about the Hue editor and I agree - ideally we want to be in a position where everything works through the editor and import/export works seamlessly. I am sure you would agree that that is not the case as of today. So - can you please answer the quesiton of where and how workflow.xml is saved before it is committed in the workspace directory? Why the reluctance to answer this quesiton already asked several times on this thread? Thanks, Martin
... View more
03-30-2015
05:49 AM
Also just to confirm - given the behaviour described in the following thread to which I just replied, workflow.xml is not updated in the workspace directory immediately when saved in Hue (as per the response it is only updated when first submitted). So whilst I have made changes to workflow definition (added extra step), the workflow.xml file is not updated in the folder. Is it then expected that the submitted coordinator will pick up those changes? Thanks, Martin
... View more
03-30-2015
05:46 AM
Hi thanks for the quick reply, I thought I saw different behaviour but it might have been my mistake. Will double check and raise support call if the expected behaviour is as you decribed and I am seeing something different. Thanks, Martin
... View more
03-30-2015
05:43 AM
2 Kudos
Hi Romain, all, I realize this is an old thread but I also feel it is counter-intuitive that the workflow.xml is not saved in the workplace the moment that the Save button is clicked. Is there a particular reason why this is the case? And to repeat the original question this thread which was not answered, where does the workflow.xml live once saved but before it is submitted? I am happy to file a bug report for this as it is causing some concerns for us. Thanks, Martin
... View more
03-30-2015
05:15 AM
Hello, Is there any way to force a submitted coordinator to pick up updated definition of the workflow? E.g. in a simple workflow with one action which runs a Hive script, if that script is updated, currently I see the only option is to kill the submitted coordinator and submit it again. Is there any other way in which it could pick up the modified Hive script? Thanks, Martin
... View more
Labels:
- Labels:
-
Apache Oozie
- « Previous
- Next »