[ 
https://issues.apache.org/jira/browse/SOLR-16691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17752825#comment-17752825
 ] 

Ishan Chattopadhyaya commented on SOLR-16691:
---------------------------------------------

Even without that workaround, what worked in the past should continue to work. 
If the bug can be fixed with the Jackson writer itself, that's good. Otherwise 
it should be fixed in the admin UI. In either case, I don't think it should be 
a blocker for changing the default response writer to Jackson. Ovidiu, thanks 
for your report. Please open a new issue.

> Use Jackson for JSON serialization
> ----------------------------------
>
>                 Key: SOLR-16691
>                 URL: https://issues.apache.org/jira/browse/SOLR-16691
>             Project: Solr
>          Issue Type: Task
>            Reporter: Noble Paul
>            Assignee: Noble Paul
>            Priority: Major
>             Fix For: 9.3
>
>          Time Spent: 2.5h
>  Remaining Estimate: 0h
>
> A user has reported significant performance gains from using Jackson over our 
> homegrown JSON writer



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org

Reply via email to