Redirect log file for tRedshiftConnection to standard output.

Highlighted
Seven Stars

Redirect log file for tRedshiftConnection to standard output.

Hi

I upgrade Talend Jobs from 6.3.1 to 7.1.1 . I have an issue with tRedshiftConnection. 

 

In  6.3.1

6.3.1.JPG

After import it to 7.1.1 , it automatically adds log file, and I cannot remove log file.

7.1.1.JPG

The job will fail if I run it on the Remote Engine, since it's on linux.

 ### Exception in component tRedshiftConnection_1  java.io.FileNotFoundException: C:/var/local/talend/source_projects/TC_V711/redshift-jdbc.log (No such file or directory) at java.io.FileOutputStream.open0(Native Method)

 

I can add a new context variable, and set it differently for dev and QA/Prod. However, I need to modify all jobs, which is not ideal. 

 

My questions:

1. It doesn't include "log file",  in the doc link https://help.talend.com/reader/1QU27dRAgeVTpWb4Bt3FMg/t2ya9FBdk8lMNyD9~6VClw  . Did I install a wrong version?

 

2. Can I redirect this log to standard output ?

 

Thanks,

Bin

 

 

Five Stars

Re: Redirect log file for tRedshiftConnection to standard output.

Hello,

 

Did anyone resolve above issue?

We have migrated/publish jobs developed in Talend studio 6.x into Talend cloud 7.1.1.

The jobs works just fine in local. However giving below error when run in cloud:

 

 

Failed   2019-05-30 17:35:13

 

tDBConnection_1 C:/Users/narasimha.mlv/Downloads/Talend-Studio-20181026_1147-V7.1.1/workspace/redshift-jdbc.log (No such file or directory)
java.io.FileNotFoundException: C:/Users/narasimha.mlv/Downloads/Talend-Studio-20181026_1147-V7.1.1/workspace/redshift-jdbc.log (No such file or directory)
at java.io.FileOutputStream.open0(Native Method)
at java.io.FileOutputStream.open(Unknown Source)
at java.io.FileOutputStream.<init>(Unknown Source)
at java.io.FileOutputStream.<init>(Unknown Source)
at java.io.FileWriter.<init>(Unknown Source)

 

Just to isolate the issue, we changed both the source and target as Oracle and it worked. No log file issue also. Where as with Redshift it is giving above error.

 

Let us know if you have come across this issue and fixed.

 

Thanks

Five Stars

Re: Redirect log file for tRedshiftConnection to standard output.

I'm using Talend Cloud Big Data Platform and we have the same behavior with the tRedshift component.

What we have done is use a Context variable for the Redshift log, in our local computers it goes to the Talend Workspace, in other environments we put it in /tmp/talend/redshift/logs/redshift-{jobname}.log

Five Stars

Re: Redirect log file for tRedshiftConnection to standard output.

Hi,

I tried in that way too but I am still facing the issue.

Is there any other approach to get the log file?

 

Thanks,

Alekhya.

Five Stars

Re: Redirect log file for tRedshiftConnection to standard output.

Did you see the screenshot I attached?

We use a Redshift connection component and drive other components off of that. If you have more than one Redshift component, make sure all of them use the correct Context. This should solve the problem "The file/path could not be found" on your other environments.

2019 GARNER MAGIC QUADRANT FOR DATA INTEGRATION TOOL

Talend named a Leader.

Get your copy

OPEN STUDIO FOR DATA INTEGRATION

Kickstart your first data integration and ETL projects.

Download now

What’s New for Talend Summer ’19

Watch the recorded webinar!

Watch Now

Best Practices for Using Context Variables with Talend – Part 2

Part 2 of a series on Context Variables

Blog

Best Practices for Using Context Variables with Talend – Part 1

Learn how to do cool things with Context Variables

Blog

Migrate Data from one Database to another with one Job using the Dynamic Schema

Find out how to migrate from one database to another using the Dynamic schema

Blog