Eric, Just to be clear, the full REST response is legitimate and valid JSON, in fact the escape characters around the quotes in the response element (COMPARE REST Response to the Response element INSIDE the REST Response) are there precisely to keep it valid. Unfortunately, what you would like is the response element that is currently a string to be a response JSON element. This would make the entire REST response a multi-level, hierarchical JSON document. Unfortunately, I am new to using Ignite as well, but I see this could be a challenge. I don't know if what you are asking is possible. But I see challenges as that would dictate a dynamic schema where each value within the response element within the REST response payload would engender a different response schema.
It sounds to me like you will need to parse the string as JSON. There are many utilities for this. I will try to look at options. Regards, Glenn On Mon, Jan 21, 2019 at 1:31 PM EMCox <[email protected]> wrote: > Glenn and Ilya, > > Can I take this string response and parse it as a JSON object using the > Ignite REST API? > > Or am I forced into a programming language such as C# or Java to perform > parse as JSON Object? I'm trying to use the Ignite REST API out of the box > and have it return valid JSON. The string Ignite returns is not valid JSON > with the escape characters included. I want to avoid having to do custom > code to parse the string as a JSON object and return it. This is an extra > step outside of the Ignite REST API I want to avoid at all cost. I do not > have a full blown programming language and project to support this > behavior. > If I am forced to do this I must write custom C# or Java programs to > perform > this function because it is not in Ignite. > > Are there any plans to have Ignite be able to return a valid JSON Object > without the escape characters? > > Thanks much, > Eric > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
