You are viewing a plain text version of this content. The canonical link for it is here.
Posted to solr-dev@lucene.apache.org by "Ryan McKinley (JIRA)" <ji...@apache.org> on 2007/05/07 19:28:15 UTC
[jira] Reopened: (SOLR-214) deficit of InputStreamReader support in
anonymous class of ContentStream
[ https://issues.apache.org/jira/browse/SOLR-214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ryan McKinley reopened SOLR-214:
--------------------------------
Without this patch, resin balks at utf-8 input
http://www.nabble.com/UTF-8-problem-with-Resin-tf3704271.html
If resin and tomcat don't handle "getReader()" correctly, maybe we should handle it explicitly
> deficit of InputStreamReader support in anonymous class of ContentStream
> ------------------------------------------------------------------------
>
> Key: SOLR-214
> URL: https://issues.apache.org/jira/browse/SOLR-214
> Project: Solr
> Issue Type: Bug
> Reporter: Koji Sekiguchi
> Attachments: UseInputStreamReader.patch
>
>
> After SOLR-197 is applied, POSTed Japanese XML contents turn into garbled characters in the index.
> I can see the garbled characters through Luke. The issue was never seen before SOLR-197.
> The cause of this problem is that the deficit of InputStreamReader support in the anonymous class of ContentStream in SolrRequestParsers.parseParamsAndFillStreams() method.
> Before SOLR-197, InputStreamReader was used in XmlUpdateRequestHandler.handleRequestBody() method:
> // Cycle through each stream
> for( ContentStream stream : req.getContentStreams() ) {
> String charset = getCharsetFromContentType( stream.getContentType() );
> Reader reader = null;
> if( charset == null ) {
> reader = new InputStreamReader( stream.getStream() );
> }
> else {
> reader = new InputStreamReader( stream.getStream(), charset );
> }
> rsp.add( "update", this.update( reader ) );
>
> // Make sure its closed
> try { reader.close(); } catch( Exception ex ){}
> }
> The patch will apply this effect to SolrRequestParsers.
> regards,
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.