tFileOutputDelimited with pipe delimiter have atypical behavior on Linux Environment
Hi guys,
I am witnessing an atypical behavior when migrating a job, developed on Windows environment to Linux.
Here's my scenario:
Content of "in.txt": 1 | 2 | 3;
The job:
Out.txt content: 3 | 2 | 1
In the Windows environment the output file is generated correctly, however, in Linux I have no errors in the execution, but the "out.txt" file is not generated. If I change the delimiter, for example, to comma, in both environments I have the expected return. Any idea why?
This is an abstraction of my actual job, by way of example.