GitHub user bamaer added a comment to the discussion: Hop Web | Airflow HTTP operator
The current Hop Server is stateless. It can't read pipelines from disk, so you'll have to register all pipelines and workflow before you can execute them there, and you'll have to repeat the process every time Hop Server is restarted. You wouldn't have that issue with the DockerOperator. Another option could be to build your workflows and pipelines in Hop Web and integrate them in a gitops process that builds fully self-contained container images that you can execute from Airflow. This would eliminate the complexity of mounting volumes to share your Hop projects, but it would introduce new complexity on the gitops side. GitHub link: https://github.com/apache/hop/discussions/6095#discussioncomment-15116076 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
