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

Karl Wright commented on CONNECTORS-674:
----------------------------------------

Hi Ryan,

After re-enabling the ability to set multipart forms in SolrJ in our local copy 
of the HttpSolrServer class, we discovered and fixed a number of other issues.  
I see you found one of them (CONNECTORS-630).  Has that also been fixed in 
Solrj 4.3?

The rest of the fixed issues are here:

------------------------------------------------------------------------
r1447556 | kwright | 2013-02-18 18:33:45 -0500 (Mon, 18 Feb 2013) | 1 line

More fixes for CONNECTORS-623.
------------------------------------------------------------------------
r1447526 | kwright | 2013-02-18 17:49:41 -0500 (Mon, 18 Feb 2013) | 1 line

Fix an NPE, part of CONNECTORS-623
------------------------------------------------------------------------
r1447262 | kwright | 2013-02-18 08:58:05 -0500 (Mon, 18 Feb 2013) | 1 line

Ok, REALLY enable multipart forms. Part of CONNECTORS-632.
------------------------------------------------------------------------
r1446153 | kwright | 2013-02-14 08:03:24 -0500 (Thu, 14 Feb 2013) | 1 line

Revisit the fix for CONNECTORS-623.  Override the HttpSolrServer class instead,
and force multipart post, in order to guarantee delivery of content type, name,
and length to SolrCell.
------------------------------------------------------------------------

I'll and CONNECTORS-623 to the related tickets accordingly.

                
> Send metadata to Solr using multipart request
> ---------------------------------------------
>
>                 Key: CONNECTORS-674
>                 URL: https://issues.apache.org/jira/browse/CONNECTORS-674
>             Project: ManifoldCF
>          Issue Type: Improvement
>          Components: Lucene/SOLR connector
>            Reporter: Ryan McKinley
>            Assignee: Karl Wright
>
> In Solrj 4.3, setUserMultipartRequest is exposed.  Rather then encoding the 
> metadata in the URL string, we should send it in the request body

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

Reply via email to