NicoDupont commented on issue #4789: URL: https://github.com/apache/hop/issues/4789#issuecomment-2637291720
I don't know if the problem could be the remote engine configuration ? In many workflows / pipelines, I have to manage multiple paths that don't necessarily have the same root. How can I define multiple paths if they are renamed? I'm not sure, but I think the DATA_PATH_1 or DATA_PATH_2 ... parameters are empty because nothing is configured in the remote engine configuration. If nothing is configured, shouldn't the paths be left hard-coded in the workflow or pipeline?  docs : Export linked resources to server This option sends not just the parent workflow to the server but also all other referenced pipelines and workflows. For example if you have pipelines or workflows referenced in actions they will be sent to the server as well. All the used pipelines and workflows together with the XML presentation of the workflow execution configuration will be sent over to the server in the form of a ZIP archive. The server receives this archive and without unzipping runs the workflow. To make this function correctly, Hop changes the references as well as references to filenames. For example ${PROJECT_HOME}/update-dimensions.hwf will be changed to ${Internal.Entry.Current.Folder}/update-dimensions.hwf. As you can see Hop will try to use a relative path to the parent file. If you have are using data files then those file names will be renamed as well. For example, you might be reading a file called ${PROJECT_HOME}/files/bigfile.csv in a CSV File Input transform. During the export the referenced filename will be changed to ${DATA_PATH_1}/bigfile.csv. For every folder that is referenced a new variable will be defined and set in the execution configuration. By default, the path set for this variable will be the same as on the executing (local) machine. On the server this might not make a lot of sense. **For this reason you can specify a reference source folder like ${PROJECT_HOME} in combination with a target folder like /server/.** In that example variable DATA_PATH_1 will get value /server/files/. This in turn allows you to transfer required files in advance or map a folder into a docker container and so on. It gives you flexibility when executing remotely while having ease of development on your client. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
