You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Uwe Schindler (JIRA)" <ji...@apache.org> on 2013/07/28 12:07:48 UTC
[jira] [Updated] (SOLR-5082) Implement ie=charset parameter
[ https://issues.apache.org/jira/browse/SOLR-5082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Uwe Schindler updated SOLR-5082:
--------------------------------
Attachment: SOLR-5082.patch
Patch.
This uses a buffering approach: It buffers all key-value pair until it sees a {{ie=CHARSET}} kv pair. It then decodes all buffered tokens and from now on directly decodes. This is the most memory efficent approach I was able to find.
> 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
>
>
> 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-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org