Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
See why IDC MarketScape names Qlik a 2025 Leader! Read more
cancel
Showing results for 
Search instead for 
Did you mean: 
yvesR
Contributor
Contributor

TOS - TRestClient call doesn't return anything when HTTP-202 and skip remaining rows !

Hello,

 

I'm working with Talend Open Studio 7.2.1 for data integration (without enterprise licence).

I'd like to use the tRestClient component to call a REST api (POST, content-type:JSON, accept-type:JSON).

If I call the API manualy with curl and my JSON, it result in a HTTP-202 response

If I call the API with the tRestClient component and the same JSON, tRestClient doesn't return anything, no response, no error and skip all remaining rows before the job ends !

I found a bug and cumulative patch fot 6.2.1 for a problem that looks like but is not the same because there is no error in my case and I'm working on 7.2.1.

I found that the problem comes form the tResclient "RESPONSE" row : When i Get an HTTP-202 response :

  • If I remove the tRestClient RESPONSE row and the associated tLog, job keeps going on
  • If I let the tRestClient RESPONSE row and the associated tLog, job skip every rows ! unbelievable !!!

So there is something wrong (or a bug !) with de RESPONSE row when I get an HTTP-202 response in tRestClient... but I don't know what :'( !!

  1. Has someone ever seen such a thing with tRestClient (HTTP-202 in tRestClient => no error, no reponse and skip remaining rows )? Is it a bug ?
  2. Are there any advice/best practice to specify good RESPONSE row in tRestClient ?
  3. Is there a way to log everything at a very low level in Talend Studio so as I can understand what is happening ?

Thanks in advance for your help,

 

Yves.

Labels (3)
2 Replies
Anonymous
Not applicable

Hi

Just look at the issue, the problem is because the response returns a empty payload, maybe the bug does still exist, can you report an issue on our bugtracker?

In the mean time, can you try to uncheck the 'convert the response to DOM Document' box and see if it resolves the issue?

 

Regards

Shong

yvesR
Contributor
Contributor
Author

Hello,

thanks for your answer.

the 'convert the response to DOM Document' is already unchecked 😞

I'l try to report the issue on the bugtracker,

Yves.