You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hop.apache.org by "hansva (via GitHub)" <gi...@apache.org> on 2026/08/26 12:25:43 UTC
[I] [Bug]: VFS connections do not work in hop server (hop)
hansva opened a new issue, #8106:
URL: https://github.com/apache/hop/issues/8106
### Apache Hop version?
2.19.0
### Java version?
21
### Operating system
Other
### What happened?
When executing pipelines/workflows on Hop Server that carry their own custom VFS destinations the pipeline would fail.
### Issue Priority
Priority: 2
### Issue Component
Component: Hop Server
--
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: issues-unsubscribe@hop.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Bug]: VFS connections do not work in hop server (hop)
Posted by "LPETIT458 (via GitHub)" <gi...@apache.org>.
LPETIT458 commented on issue #8106:
URL: https://github.com/apache/hop/issues/8106#issuecomment-5510424829
We noticed that the metadata related to the pipeline/workflow is actually present in the zip file when "Export linked resources to server" is checked in the run configuration. Why doesn't Hop Server use it?
--
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: issues-unsubscribe@hop.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Bug]: VFS connections do not work in hop server (hop)
Posted by "hansva (via GitHub)" <gi...@apache.org>.
hansva commented on issue #8106:
URL: https://github.com/apache/hop/issues/8106#issuecomment-5510530556
Because it would break every running workflow/pipeline at that point in time.
The filesystems were 1 shared thing; this worked perfectly when using hop-run or your local GUI instance. Each JVM would build it's own filesystem based on the project on startup and this works fine.
When we go to Hop Server where multiple projects/configurations can run at the same time, this would have given issues.
I could have 2 different projects both using `test://` but with a totally different configuration. they would invalidate each other.
And as the file-systems were a single shared thing, it would also close all existing connections and recreate them causing all running processes to lose access to their current filesystem.
It was an architectural problem which we missed when we introduced the option to create file systems on project level.
--
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: issues-unsubscribe@hop.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Bug]: VFS connections do not work in hop server (hop)
Posted by "hansva (via GitHub)" <gi...@apache.org>.
hansva commented on issue #8106:
URL: https://github.com/apache/hop/issues/8106#issuecomment-5511306012
Or just test with our Development version?
--
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: issues-unsubscribe@hop.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Bug]: VFS connections do not work in hop server (hop)
Posted by "hansva (via GitHub)" <gi...@apache.org>.
hansva commented on issue #8106:
URL: https://github.com/apache/hop/issues/8106#issuecomment-5510183120
This is a setup I haven't tested. I would assume they resolve then.
If the server is started with either the project parameter or using the `<metadata-folder>` tags in the XML. You do need to restart the server if new items/changes are made to these objects, they are not loaded/refreshed on each execution.
--
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: issues-unsubscribe@hop.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Bug]: VFS connections do not work in hop server (hop)
Posted by "hansva (via GitHub)" <gi...@apache.org>.
hansva commented on issue #8106:
URL: https://github.com/apache/hop/issues/8106#issuecomment-5425272474
.take-issue
--
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: issues-unsubscribe@hop.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Bug]: VFS connections do not work in hop server (hop)
Posted by "LPETIT458 (via GitHub)" <gi...@apache.org>.
LPETIT458 commented on issue #8106:
URL: https://github.com/apache/hop/issues/8106#issuecomment-5511277842
Thanks for the clarification. We're going to try spinning up a remote Hop Server process that reloads the metadata and only handles a single execution, then tearing that process down once it's finished. That still leaves the question of how monitoring would work in that setup. I'll ask on the ticket whether there's another way to work around this issue as well. Thanks a lot for your help.
--
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: issues-unsubscribe@hop.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Bug]: VFS connections do not work in hop server (hop)
Posted by "LPETIT458 (via GitHub)" <gi...@apache.org>.
LPETIT458 commented on issue #8106:
URL: https://github.com/apache/hop/issues/8106#issuecomment-5510108121
Does this limitation also apply when the S3 connection metadata is shared via NFS between Hop GUI and Hop Server (i.e. same NFS mount, same metadata path, on both sides)? In our setup the connection definition itself isn't transmitted as part of a resource bundle — it's already present locally on the server through the shared NFS mount, using the exact same path as on the client. We'd expect the server to resolve it from its own local metadata in that case, but we're still seeing the connection name substituted literally instead of being resolved.
--
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: issues-unsubscribe@hop.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Bug]: VFS connections do not work in hop server (hop)
Posted by "hansva (via GitHub)" <gi...@apache.org>.
hansva closed issue #8106: [Bug]: VFS connections do not work in hop server
URL: https://github.com/apache/hop/issues/8106
--
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: issues-unsubscribe@hop.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org