You are not logged in.

Unanswered posts



Important! This site has been replaced. All content here is read-only. Please visit our brand-new community at https://community.talend.com/. We look forward to hearing from you there!



#1 2017-03-10 13:06:23

Cascade2nd
Guest

Cascade2nd said:

Switched to Taled OS 6.3 -> imported 5.6 project will not compile

Tags: [error, java]

Hi
We have a working 5.6 project and now switched to TOS 6.3, imported the project and it creates compile errors. It's a simple job, checking a FTP server for files, determining which one was allready imported to the database and retrieve only newer files.
When running the job, TOS creates an error saying
Detail Message: nb_line_tLogRow_2 cannot be resolved to a variable
The original error message related to an tFTP componend, which we removed and replaced with a tLogRow component but the error persists.
The funny thing is, when we remove any compontent after the tMap deciding which file to load and which to skip (using a reject), the job will compile without errors and run.
But placing any component in the tMap reject path, it will cause the compilation error.
Did anyone experience this issue before? Any solution?

#2 2017-03-13 04:17:32

xdshi
Talend Team


xdshi said:

Re: Switched to Taled OS 6.3 -> imported 5.6 project will not compile

Hi,
What's the  JDK version you are using? Are you using JDK 1.8 for your V 6.3?
Could you please try to re-create a new job to see if this issue repro?
Best regards
Sabrina


What we can do is to make sure that Talend will be your best choice!

Offline

#3 2017-03-17 09:30:46

Cascade2nd
Guest

Cascade2nd said:

Re: Switched to Taled OS 6.3 -> imported 5.6 project will not compile

We are using JDK 1.8 with TOS 6.3
When creating a new job (simple Testjob) everything works fine. We allready recreated the job with the compile error, but when we add a second tFTPGet, the compile error appears again. Even if we replace both tFTPGet with a simple tLogRow, it appears, when adding the second tLogRow.
So, it might be, that the error results in an previous compontent but will only cause the error, if a second component of that type (tLogRow or tFTPGet) is added.

#4 2017-03-17 09:48:33

xdshi
Talend Team


xdshi said:

Re: Switched to Taled OS 6.3 -> imported 5.6 project will not compile

Hi,
Could you please show us your job design screenshots? Does this compile issue repro on this specific FTP job or all imported jobs?
Best regards
Sabrina


What we can do is to make sure that Talend will be your best choice!

Offline

#5 2017-03-17 10:12:56

rhall_2.0
Member
1251 posts

rhall_2.0 said:

Re: Switched to Taled OS 6.3 -> imported 5.6 project will not compile

I've seen this behaviour before and for me it turned out to be a corrupt tMap component. I have had it a handful of times in 7 or 8 years of using Talend. Try replacing the tMap with a new one, configure it again (I know, its a pain) and give it another go.


rilhiaSolutionsLogo_0.png

Offline

#6 2017-03-17 13:17:31

Cascade2nd
Member
4 posts

Cascade2nd said:

Re: Switched to Taled OS 6.3 -> imported 5.6 project will not compile

Tried to recreate the tMap compontents (in fact, the complete job), but still not working.
I've attached 2 screenshots. The first one has only on tFTPGet and severel tLogRow components. With this structure, the job runs as desired. But when replacing the tLogRow component with a tFTPGet, we get errors for 3 components (2 of them worked fine in the first screenshot). When we remove the tFTPGet component in screenshot 2, job is compiled successfully and runs.
Is there any restriction for a tFTPGet? In version 5.6 we were able to use multiple tFTPGet components in one job without any errors :-(



mini_blob_20170317-0520.png
mini_blob_20170317-0522.png

Last edited by Cascade2nd (2017-03-17 13:22:28)

Offline

#7 2017-03-23 09:44:59

Cascade2nd
Member
4 posts

Cascade2nd said:

Re: Switched to Taled OS 6.3 -> imported 5.6 project will not compile

Anyone an idea? Thx

Offline

#8 2017-03-23 11:51:09

rhall_2.0
Member
1251 posts

rhall_2.0 said:

Re: Switched to Taled OS 6.3 -> imported 5.6 project will not compile

Can you take a screenshot of line 4416 (and the code around it) on the code tab. The code tab can be seen in your second image about halfway down the image on the left. 


rilhiaSolutionsLogo_0.png

Offline

#9 2017-03-28 09:02:12

Cascade2nd
Member
4 posts

Cascade2nd said:

Re: Switched to Taled OS 6.3 -> imported 5.6 project will not compile

Not the code from the original screenshot but the same issue. We tried to modify the code but allways same problem (even after recreation)
mini_blob_20170328-0102.png

Last edited by Cascade2nd (2017-03-28 09:02:42)

Offline

#10 2017-03-29 13:42:32

Cascade2nd
Member
4 posts

Cascade2nd said:

Re: Switched to Taled OS 6.3 -> imported 5.6 project will not compile

It seems to us, that the code generation of the tMap components has some weird behaviour.
When we change the order of the output links of the tMap, the code generator moves the error to other components.
It only occours, when other components than tLogRow are used. With the tLogRow, everything is fine and the output of the log is as desired.
What we try to archive is the following
- retrieve filelist from ftp
- check for each file, if any is allready downloaded and has an entry in MySQL database
- if file is not in DB, tFTPGet it, put into local directory and insert DB dataset with new file information
- if file is in DB, compare file timestamp to the one in DB
- if file is newer than the DB entry, tFTPGet it, put into local directory (overwrite old one) and insert DB dataset with new file information (versioned)
Maybe we use the wrong method here :-/

Thx

Offline

Board footer

Talend Contributor Agreement - Talend Website Privacy Policy