[ 
https://issues.apache.org/jira/browse/SOLR-2350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hoss Man updated SOLR-2350:
---------------------------

    Attachment: SOLR-2350.patch

Attached file makes a bunch of changes to SimplePostTool.java, notably:

* stop using Reader/Writer - stream bytes directly
* use application/xml as default mime-type, but let user override
* look at HTTP status to determine if there is an error (instead of string 
comparisons on the response)
* ignore the response body from the POST by default, but let the user choose to 
see it

...the last two making it more feasible to use this when dealing with things 
like that Document Analysis tool (since you can now see the response if you 
want)

The patch also includes a gb2312-example.xml similar to the utf8-example.xml 
showing off non-ascii characters.  the big hitch here is that i'm only guessing 
that this really a properly encoded gb2312 -- i did the best i could to make my 
editor create one, but i have no idea if it worked properly.  it seems to index 
correctly, but for all i know it's really still just UTF-8


> improve post.jar to handle non UTF-8 files
> ------------------------------------------
>
>                 Key: SOLR-2350
>                 URL: https://issues.apache.org/jira/browse/SOLR-2350
>             Project: Solr
>          Issue Type: Improvement
>            Reporter: Hoss Man
>            Assignee: Hoss Man
>             Fix For: 3.1, 4.0
>
>         Attachments: SOLR-2350.patch
>
>
> thanks to all the awesomeness Uwe did in SOLR-96, some hard coded 
> limitations/assumptions in the simple post.jar provided for the example files 
> can be cleaned up.
> notably: it use to deal with Readers/Writers, and warned people there data 
> had to be UTF-8 (because that's all Solr supported) and now it can deal with 
> raw streams

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to