Can't figure out how to pass a whole origin Json to HTTP Client

asked 2018-11-13 22:12:30 -0600

Carmonium gravatar image


I've tried hardly to pass the whole Json data coming from an API REST Origin, to an HTTP Client stage.

All the time I get "Error 400: Couldn't find the resource..." message. Last attempt was {record:value('/variables)'}, in the Request-Data field.

I think my problem is to get to the right syntax for that field, because I tried Http-Client in an isolated pipeline putting json data directly in Request-Data field and it worked.

Please, any tip will be preciated.

Thanks in advance

Luis Carmona

edit retag flag offensive close merge delete


What is the error you are seeing? Looking at the example you pasted, I notice that the single quotes and parentheses are not balanced in the EL expression.

jeff gravatar imagejeff ( 2018-11-14 10:33:42 -0600 )edit

Hi Jeff, Sorry for the mistype, it was only in my question text, in the configuration it is well written. ${record:value('/')} The error that pipeline throws is: HTTP_01 - Error fetching resource. Status 400: Reason: Bad Request. The previous stage is HTTP Server, with output in JSON format.

Carmonium gravatar imageCarmonium ( 2018-11-16 12:15:16 -0600 )edit

What do you have set for Request Transfer Encoding?

iamontheinet gravatar imageiamontheinet ( 2018-11-16 15:43:46 -0600 )edit

I have "BUFFERED". I did a try with a Camunda destination, and it worked. So something special is about POSTING to ElasticSearch (version 6.5)

Carmonium gravatar imageCarmonium ( 2018-11-16 15:46:11 -0600 )edit

I tryed Elastic stage as well, and it did work two. My problem is that I need a Processor stage, and the Elastic one is available only as Destiny

Carmonium gravatar imageCarmonium ( 2018-11-16 15:52:18 -0600 )edit