[
https://issues.apache.org/jira/browse/SOLR-4685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14521413#comment-14521413
]
Noble Paul edited comment on SOLR-4685 at 4/30/15 12:21 PM:
------------------------------------------------------------
I fail to see , how can you claim that this is completely backward compatible.
What if I already have a field with an "_json" suffix and I have coded my
client app to read escaped JSON string?
I totally understand the motivation and need for this . Probably , we should
add an extra request flag to turn this on . like {{json.key.suffix=_json}}.
Which means any field ending with {{_json}} will be unescaped
was (Author: noble.paul):
I fail to see , how can you claim that this is completely backward compatible.
What if I already have a field with an "_json" suffix and I have coded my
client app to read escaped JSON string?
I totally understand the motivation and need for this . Probably , we should
add an extra request flag to turn this on . like {{raw.json.suffix=_json}}.
Which means any field ending with {{_json}} will be unescaped
> 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
> Priority: Minor
> Attachments: SOLR-4685.1.patch, SOLR-4685.5.1.patch,
> SOLR-4685.SOLR_4_5.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.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
