LPETIT458 commented on issue #8234:
URL: https://github.com/apache/hop/issues/8234#issuecomment-5511360221

   While waiting for an architectural fix, is there another workaround we could 
put in place? The approach we're considering (a dedicated, ephemeral remote Hop 
Server process per execution, restarted each time to reload the metadata) would 
work, but it comes with a real cost: JVM startup time and project reload on 
every single execution, which becomes a real penalty if pipelines are short or 
frequent. Is there an approach that would allow VFS connections to be isolated 
per execution within a single running server process, without having to spin up 
a whole new process each time?


-- 
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]

Reply via email to