Six Stars

Compilation error in tHashInput

Hi All,

 

I was using the tHashOuput/tHashInput components in my job (when using Talend 5.5.1). But when the same job was migrated to Talend 6.3 - it is showing the below error.

I tried to create a simple job in 6.3 with tHash components (attached) - but same error.

 

Execution failed : Job compile errors
At least job "Test" has a compile errors, please fix and export again.
Error Line: 1296
Detail Message: The method remove(String) is undefined for the type MapHashFile.TalendMultiThreadLockMap
There may be some other errors caused by JVM compatibility. Make sure your JVM setup is similar to the studio.

 

Thanks in advance,

J

- JG
1 ACCEPTED SOLUTION

Accepted Solutions
Six Stars

Re: Compilation error in tHashInput

The problem with tHashInput/Output components were resolved with the following steps,

1. Exit talend studio

2. Delete the (org\talend\libraries\thashfile\6.0.0\)thashfile-6.0.0.jar from maven local repo

3. Delete the same file from Nexus repo as well

4. Start talend studio and try running the job again

- JG
5 REPLIES
Twelve Stars

Re: Compilation error in tHashInput

What version of Java are you using? I believe it should v1.8 for Talend 6.3

Rilhia Solutions
Six Stars

Re: Compilation error in tHashInput

Yes i am using JDK 1.8 (jre1.8.0_91)

- JG
Moderator

Re: Compilation error in tHashInput

Hello,

Does this compilation error repro on all jobs or a specific job?

Best regards

Sabrina

--
Don't forget to give kudos when a reply is helpful and click Accept the solution when you think you're good with it.
Six Stars

Re: Compilation error in tHashInput

Its on all jobs in the repo which uses the tHash components. 

- JG
Six Stars

Re: Compilation error in tHashInput

The problem with tHashInput/Output components were resolved with the following steps,

1. Exit talend studio

2. Delete the (org\talend\libraries\thashfile\6.0.0\)thashfile-6.0.0.jar from maven local repo

3. Delete the same file from Nexus repo as well

4. Start talend studio and try running the job again

- JG