Java Error with org.talend.daikon

[Anonymous]

My job uses the tDataStewardshipTaskInput component to read completed tasks from the Talend Data Stewardship console and write the golden records to Hive. Right now, it throws the following error:

Exception in thread "main" java.lang.NoSuchMethodError:

org.apache.http.impl.conn.PoolingHttpClientConnectManager.setValidateAfterInactivity

  at org.apache.http.client.fluent.Executor.<clinit>[Executor.java:99]

  at org.talend.components.datastewardship.connection.TdsConnection.<init> (TdsConnection.java:77)

  at org.talend.components.datastewardship.runtime.TdsSourceOrSink.validateConnection (TdsSourceOrSink.java:118)

  at org.talend.components.datastewardship.runtime.TdsSourceOrSink.validate (TdsSourceOrsink.java:104)

  at pmdevelopment.testdatastewardshipinput_0_1.testDataStewardshipInput.tDataStewardshipTaskInput_1Process(testDataStewardshipInput.java:3637)

  at pmdevelopment.testdatastewardshipinput_0_1.testDataStewardshipInput.tHDFSConnection_1Process(testDataStewardshipInput.java:508)

  at pmdevelopment.testdatastewardshipinput_0_1.testDataStewardshipInput.runJobInTOS(testDataStewardshipInput.java:5285)

  at pmdevelopment.testdatastewardship_0_1.testDataStewardshipInput.main(testDataStewardshipInput.java:5072)

(Sorry for any typos: I had to type the stack trace by hand for some bizarre reason)

Setting a breakpoint on tDataStewardshipTaskInput and tracing the code execution in Java shows the error is indeed caused by the following line:

org.talend.daikon.properties.ValidationResult vr tDataStewardshipTaskInput_1 = sourceOrSink_tDataStewardshipTaskInput_1.

  validate(container_tDataStewardshipTaskInput_1);

So my question is, does this method actually exist? And if so, do I need to download an external .jar file to use it? Or is this a red herring, and something else is causing the error?

Thanks,

David

[Anonymous]

Hello,

Could you please indicate on which build version you got this issue? Screenshots of your component setting will be preferred.

Best regards

Sabrina

[Anonymous]

Wow, I queried an error in TDS today, and the only hit I got was my own question from last year. That's...interesting.

If anyone else gets this error, check to see if the input schema matches the TDS schema EXACTLY. This includes the field names: if you have a field named "customer_id" and you map it to a TDS field named "Customer_id", it won't work. This may be because Java is case-sensitive, although I've never had that be an issue in schema mappings before. Forewarned is forearmed.

[Anonymous]

Hello,

---

@DVSCHWAB wrote:
Wow, I queried an error in TDS today, and the only hit I got was my own question from last year. That's...interesting.

If anyone else gets this error, check to see if the input schema matches the TDS schema EXACTLY. This includes the field names: if you have a field named "customer_id" and you map it to a TDS field named "Customer_id", it won't work. This may be because Java is case-sensitive, although I've never had that be an issue in schema mappings before. Forewarned is forearmed.

---

Can we consider this topic as resolved? You can click "Accept as Solution" button to mark your topic as resolved.

Best regards

Sabrina