[
https://issues.apache.org/jira/browse/SOLR-4685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13702133#comment-13702133
]
Jack Krupansky commented on SOLR-4685:
--------------------------------------
To me, this feels like too much of a hack than a carefully designed feature. Or
maybe it's just the hard-wired field naming convention, or that this is
JSON-specific - don't XML, PHP, Ruby, etc., have a similar issue?
Maybe it would be better if you simply had a custom, application-specific
response writer.
Or, why not just have the client parse JSON string values? I mean, that is easy
to do in both Java and JavaScript, right?
So, I'm missing out on why this should be a feature of Solr. I mean, Solr's
responsibility is to return the values of the fields, not format them in an
application-specific manner.
> 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
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
