Qlik Talend ESB: cSetHeader JSONPath Parsing removes Double Quotes which produces Invalid JSON

wei_guo — Wed, 10 Dec 2025 08:55:02 GMT

After upgrading from Talend 7.3 to Talend 8 (R2025-10), it includes the Camel 4 update, and a change in the cSetHeader component. In previous Talend 7.x, JSONPath evaluation generated a correctly formatted JSON header, however, in Talend 8, the same configuration produces a non-JSON representation where double quotes are stripped from the resulting object.

For example

Source Input

{ "META": {"Correlation_ID": "B","BGM_ACTION_CODE": “A”},
 "STATUS": {"ADD_R_UPDATE_SUCCEEDED": “Y”},
 "ERR": [ {"field": "ADD","keyword": "custOrgMustHaveAdd", "entity": “ORGANI” }]
}

cSetHeader Component Setting

Name	"ERR"
Language	jsonPath
Value	"$.ERR[*]"

Output in Talend 7 (Correct)

[{"field":"ADD","keyword":"custOrgMustHaveAdd","entity":"ORGANI"}]

cSetHeaderOutputTalend7

Output in Talend 8 (Invalid JSON format with out Double Quotes)

[{field=ADD, keyword=custOrgMustHaveAdd, entity=ORGANI}]

cSetHeaderOutputTalend8

Resolution

Install the latest R2025-11 (or newer) update for both Talend Studio and Talend Runtime, where the corrected behavior has been implemented.

Cause

This behavior stems from changes in the underlying JSON processor, specifically, the shift from json-smart to JacksonJsonProvider, which modifies how JSONPath results are serialized.

The issue aligns with the upstream Camel defect jira issue reported here:
CAMEL-16389 | issues.apache.org

article Qlik Talend ESB: cSetHeader JSONPath Parsing removes Double Quotes which produces Invalid JSON in Official Support Articles

Qlik Talend ESB: cSetHeader JSONPath Parsing removes Double Quotes which produces Invalid JSON

Resolution

Cause

Environment