[
https://issues.apache.org/jira/browse/CONNECTORS-254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13104317#comment-13104317
]
Karl Wright commented on CONNECTORS-254:
----------------------------------------
It appears that the major difference is that curl's POST is not a multi-part
post. It's apparently the multi-part form post with zero-length content that
Solr (or Jetty) doesn't like.
The Solr connector must use multi-part in order to include other fields such as
metadata, so it's not an option to do things just like post.sh does. Can you
modify the curl POST command to do a multi-part form post, and try that with a
zero-length file? Then we can really compare apples against apples.
> Bad request when posting 0 byte file to Solr
> --------------------------------------------
>
> Key: CONNECTORS-254
> URL: https://issues.apache.org/jira/browse/CONNECTORS-254
> Project: ManifoldCF
> Issue Type: Bug
> Components: Lucene/SOLR connector
> Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF 0.3
> Reporter: Shinichiro Abe
> Priority: Minor
> Fix For: ManifoldCF 0.3
>
> Attachments: CONNECTORS-254-1.patch, sample0byte.zip
>
>
> It seems that httpposter brings about bad request when posting 0 byte file.
> Solr log say the below. "missing content stream". Status code is 400.
> On the other hand when using Solr request handler without MCF, this exception
> is not thrown and the posting 0 byte files is indexed normally.
>
> 2011/09/13 12:30:40 org.apache.solr.core.SolrCore execute
> ???: [] webapp=/solr path=/update/extract
> params={literal.id=file:/Users/abe/Desktop/1/no-content/no-content.txt&literal.uri=/Users/abe/Desktop/1/no-content/no-content.txt}
> status=400 QTime=367
> 2011/09/13 12:30:40 org.apache.solr.common.SolrException log
> ?v???I: org.apache.solr.common.SolrException: missing content stream
> at
> org.apache.solr.handler.ContentStreamHandlerBase.handleRequestBody(ContentStreamHandlerBase.java:62)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
