[
https://issues.apache.org/jira/browse/SOLR-4685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13787766#comment-13787766
]
Bill Bell commented on SOLR-4685:
---------------------------------
Can we please commit this ?
I am using it in PROD for last few months and it works great.
Jack: XML, PHP, Ruby don't have this issue since if the field is XML, and you
use wt=xml you get XML normally out of it. But when you set wt=json and have a
field that is JSON string, it escapes everything. There is no hard in this. It
just stops the escaping of any fields that end with json.fsuffix=_json -
basically ending with _json.
I need all the other features of wt=json, but I also need the ability to NOT
escape a JSON string field.
If someone could figure out a simple way that does not waste resources figuring
out which fields are already JSON when you use wt=json, that would be
preferrable - to turn off escaping of that field. But until we have that I am
proposing this feature. Which has NO hard and it a simple feature to maintain -
"turn off escaping of a field when using wt=json".
Can we vote on it?
> JSON response write modification to support RAW JSON
> ----------------------------------------------------
>
> Key: SOLR-4685
> URL: https://issues.apache.org/jira/browse/SOLR-4685
> Project: Solr
> Issue Type: Improvement
> Reporter: Bill Bell
> Assignee: Erik Hatcher
> Priority: Minor
> Attachments: SOLR-4685.1.patch
>
>
> If the field ends with "_json" allow the field to return raw JSON.
> For example the field,
> office_json -- string
> I already put into the field raw JSON already escaped. I want it to come with
> no double quotes and not escaped.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
