You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[Bug]: Text File Output, the file is not created when executing on a remote server and using the filename instead of the filename from field option.
#4789
Open
NicoDupont opened this issue
Jan 16, 2025
· 6 comments
When workflow/pipeline is executed on remote serveur and if I use the filename, the file is not created and there is no error.
When I use the filename from field option, it works well like as expected.
I do some tests with network path, local path and/or parameter.
I got always the same result.
No problem if I use the filename via hop gui and local execution.
thx !
Issue Priority
Priority: 2
Issue Component
Component: Hop Server
The text was updated successfully, but these errors were encountered:
There's a strange behavior because when I don't put anything in the file name. I get an error at runtime.
but if I write something like "anything" the execution doesn't generate an error.
On hop gui local execution it works with this 2 options on the Filename
\\serveurname\Import_Export\e-TMS\in\vehicules\vehicules
or E:\Import_Export\e-TMS\in\vehicules\vehicules
On remote serveur nothing work except using the option filename from field
on field I put :
\\serveurname\Import_Export\e-TMS\in\vehicules\vehicules
OR
E:\Import_Export\e-TMS\in\vehicules
and it works as expected
Apache Hop version?
2.11
Java version?
22
Operating system
Windows
What happened?
jdk 22
hop 2.10 or 2.11
Text File Output
When workflow/pipeline is executed on remote serveur and if I use the filename, the file is not created and there is no error.
When I use the filename from field option, it works well like as expected.
I do some tests with network path, local path and/or parameter.
I got always the same result.
No problem if I use the filename via hop gui and local execution.
thx !
Issue Priority
Priority: 2
Issue Component
Component: Hop Server
The text was updated successfully, but these errors were encountered: