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

Shawn Heisey commented on SOLR-4358:
------------------------------------

[~kwri...@metacarta.com] It has been committed into trunk (5.0) and branch_4x 
(4.4).  The commits happened on April 19th, which is after the 4.3 branch was 
created.

I thought I remembered a discussion on a vote thread for 4.3 about a fix for a 
multi-part mime issue that went into one of the later release candidates, but 
now I can't find it, so it must have happened only in my mind.  I 
double-checked the 4.3 code branch and this is NOT included.

I believe that it's now too late to get it into 4.3.  You have the option of 
building branch_4x if you need the fix now.

                
> SolrJ, by preventing multi-part post, loses key information about file name 
> that Tika needs
> -------------------------------------------------------------------------------------------
>
>                 Key: SOLR-4358
>                 URL: https://issues.apache.org/jira/browse/SOLR-4358
>             Project: Solr
>          Issue Type: Bug
>          Components: clients - java
>    Affects Versions: 4.0
>            Reporter: Karl Wright
>            Assignee: Ryan McKinley
>         Attachments: additional_changes.diff, SOLR-4358.patch, 
> SOLR-4358.patch, SOLR-4358.patch
>
>
> SolrJ accepts a ContentStream, which has a name field.  Within 
> HttpSolrServer.java, if SolrJ makes the decision to use multipart posts, this 
> filename is transmitted as part of the form boundary information.  However, 
> if SolrJ chooses not to use multipart post, the filename information is lost.
> This information is used by SolrCell (Tika) to make decisions about content 
> extraction, so it is very important that it makes it into Solr in one way or 
> another.  Either SolrJ should set appropriate equivalent headers to send the 
> filename automatically, or it should force multipart posts when this 
> information is present.

--
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

Reply via email to