tFileOutputDelimited with pipe delimiter have atypical behavior on Linux Environment

Anonymous — Sat, 16 Nov 2024 07:30:59 GMT

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.

Thank you all at once.

Version of Talend 6.4.0
Java version 1.8.0.161

Re: tFileOutputDelimited with pipe delimiter have atypical behavior on Linux Environment

Anonymous — Tue, 16 Oct 2018 06:53:09 GMT

Hello,

What's Linux environment are you using?

From your screenshots and description, it looks like the input component cannot handle a pipe directly in Linux environment.

Best regards

Sabrina

topic tFileOutputDelimited with pipe delimiter have atypical behavior on Linux Environment in Talend Studio

tFileOutputDelimited with pipe delimiter have atypical behavior on Linux Environment

Re: tFileOutputDelimited with pipe delimiter have atypical behavior on Linux Environment