[
https://issues.apache.org/jira/browse/SOLR-17009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17772014#comment-17772014
]
Chris M. Hostetter commented on SOLR-17009:
-------------------------------------------
Skimming the changes in this jira, I think the problem is simply that
{{JacksonJsonWriter}} is miss-configuring (or perhaps more accurately: "under
configuring") the {{DefaultPrettyPrinter}} so that it (y default) respects the
{{"line.separator"}} -- which is not ideal in solr.
I'm guessing the test added here just happene to be the first thing to
notice/expose the problem?
Educated googling suggests that the correct behavior for {{JacksonJsonWriter}}
is to call...
{code}
.withObjectIndenter(new DefaultIndenter().withLinefeed("\n"))
{code}
...but i don't know if there is a similar concern / indenter option with arrays?
*
https://github.com/FasterXML/jackson-databind/issues/585#issuecomment-643163524
* https://github.com/FasterXML/jackson-core/pull/166/files
> json.wrf parameter ignored in JacksonJsonWriter
> -----------------------------------------------
>
> Key: SOLR-17009
> URL: https://issues.apache.org/jira/browse/SOLR-17009
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: JSON Request API
> Affects Versions: 9.3
> Reporter: Chris Stewart
> Assignee: Alex Deparvu
> Priority: Blocker
> Fix For: 9.4
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> When requesting json output in 9.3 using json.wrf to trigger a JSONP request,
> the return is not wrapped in a function and is instead returned as a plain
> JSON object
> My test cases are:
> wt=json&json.wrf=ng_jsonp_callback_0 on Solr 9.3.0
> { "responseHeader":{ "status":0, "QTime":9, "params":{
> wt=json&json.wrf=ng_jsonp_callback_0 on Solr 7.3.1
> ng_jsonp_callback_0({ "responseHeader":{ "status":400, "QTime":206,
> "params":{
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
