[
https://issues.apache.org/jira/browse/SOLR-5082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13722988#comment-13722988
]
Uwe Schindler commented on SOLR-5082:
-------------------------------------
[~elyograg]: Are you fine with this code?
>From my tests here I have seen no slowdown for query-string parsing, it is as
>fast as before, every slowdown is smaller than measureable. In any case, the
>current URLDecoder is much more efficient than the one embedded into Jetty
>(the one with broken UTF8 in earlier versions). The slowest part in the whole
>code is MultiMapSolrParams#add, because it reallocates arrays all the time on
>duplicate keys...
> Implement ie=charset parameter
> ------------------------------
>
> Key: SOLR-5082
> URL: https://issues.apache.org/jira/browse/SOLR-5082
> Project: Solr
> Issue Type: Improvement
> Affects Versions: 4.4
> Reporter: Shawn Heisey
> Assignee: Uwe Schindler
> Priority: Minor
> Fix For: 5.0, 4.5
>
> Attachments: SOLR-5082.patch, SOLR-5082.patch
>
>
> Allow a user to send a query or update to Solr in a character set other than
> UTF-8 and inform Solr what charset to use with an "ie" parameter, for input
> encoding. This was discussed in SOLR-4265 and SOLR-4283.
> Changing the default charset is a bad idea because distributed search
> (SolrCloud) relies on UTF-8.
--
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
