Details
Description
Is there a way to make Hue create a new workspace when importing an Oozie workflow instead of using "deployment_dir" field and failing when this field is a directory that doesn't exist in the cluster?
Currently, imported oozie workflows use the "deployment_dir" field, within the workflow JSON file. If it points to a directory that doesn't exist, Hue gives the following error and fails to submit the Oozie job:
Hue Error:
[07/Jun/2018 16:22:11 +0100] models2 ERROR The copy of the deployment directory failed: FileNotFoundException: File /user/hue/oozie/workspaces/hue-oozie-1525873111.27 does not exist. (error 404). [07/Jun/2018 16:22:11 +0100] middleware INFO Processing exception: The copy of the deployment directory failed: FileNotFoundException: File /user/hue/oozie/workspaces/hue-oozie-1525873111.27 does not exist. (error 404).: Traceback (most recent call last):
PopupException: The copy of the deployment directory failed:
Manually creating the directory fixed the issue and allowed the oozie job to run without error, but it seems like Hue should create this deployment directory on its own for an imported oozie workflow if the directory doesn't exist.