Where does Hue Oozie editor store the workflow.xml file?

[#1]

Where does Hue Oozie editor store the workflow.xml file? I do not see it in the workspace.

When I create a new workflow, I specify "HDFS deployment directory". I expected that the workflow file would appear there. 

Is there a means to specify where Oozie should store the workflow.xml file?

[#2]

When you submit is, the workflow.xml should be generated in the workspace.

Romain

[#3]

So the editable version of the workflow.xml file is stored someplace else? 

If I edit or replace the workflow.xml file in the workspace, are those changes ignored and replaced when I submit the workflow?

[#4]

The workflow.xml is not editable as it will be replaced when the workflow
is submitted again.

If some XML is missing you could tell us what that way we could improve the
editor and remove the need to manually edit the XML.

Romain

[#5]

I like that the Oozie dashboard gives a visual representation of the workflow, shows the progress of each step and enables the user to kill, suspend and restart the workflow. However, I would prefer to edit the XML in my workspace, check it in to version control and deploy it to the cluster.

[#6]

Yes, in Hue 3.5 the workflow editor as an export button to export the XML
of the workflow.

Versioning built in Hue is on the roadmap (and also we will see for git
integration + global export/import
https://issues.cloudera.org/browse/HUE-1660).

Romain

[#7]

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

[#8]

The point of the editor is to not have the end user worry about any XML, if
there are some missing features in the editor, feel free to open jiras!

workflow.xml and their metadata will be easily exportable/importable in Hue
4 and https://issues.cloudera.org/browse/HUE-1660

Romain

[#9]

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

[#10]

This is a potential feature that is simply not implemented yet,

Romain