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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
