topic tHTTPClient not behaving as documented in Talend Studio

tHTTPClient not behaving as documented

NL_George — Wed, 10 Sep 2025 11:57:46 GMT

I'm following https://help.qlik.com/talend/en-US/components/8.0/http/thttpclient-schema-and-output

And I am trying to recreate the key/pair example showing

name, type String.
full_address, type String.
first_car_brand, type String.

But when I have the exact same configuration, the response my tHTTPComponent gives is this:

tLogRow_1
name = Peter
full_address = bd prairie au duc, 44000, Nantes
first_car_brand = ["Ford"]

As you can see, the first car brand is still in a JSON array instead of the single string value I was expecting.
Any ideas on how to get the response as given in the example?

Re: tHTTPClient not behaving as documented

Denis_Segard — Thu, 11 Sep 2025 08:32:49 GMT

Hello,
I noticed the same "behavior".
It would be better to open a case for the support in order to involve R&D if needed.

Kind regards

Re: tHTTPClient not behaving as documented

NL_George — Thu, 18 Sep 2025 12:11:32 GMT

Hi Denis,

I'm working on getting a support case in but my Qlik / Talend account are not working properly.
Currently trying to get the support case in through our 3rd party.

Once I get more detail from them / Qlik support I'll update this post.

Re: tHTTPClient not behaving as documented

NL_George — Tue, 14 Oct 2025 08:02:02 GMT

Update from Qlik support, apparently this behaviour is as expected.

Notable fixes and known issues | Talend Release Notes Help

Which means that if you want to follow the example from the documentation pages, you should add the JVM parameter:

-Dorg.talend.components.common.dssldictionary.DSSLDictionary.SINGLE_ELEMENT_NOT_ARRAY=true