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

Karl Wright commented on CONNECTORS-1533:
-----------------------------------------

The rejections I see have the following form:

{code}
Error from server at http://localhost:8394/solr/collection1: ERROR: 
[doc=file:/C:/wip/mcf-release-scripts/release-scripts/.svn/pristine/db/db0ad7d88277f4e7ab862049c928c40b797be9de.svn-base]
 Error adding field 'stream_size'='null' msg=For input string: "null"
{code}

Some documents succeed, and some fail with this.  The failures have response 
code 400, which means they don't get indexed.  I can see no reason why some 
succeed and some fail.


> Solr Connector is unable to ingest documents
> --------------------------------------------
>
>                 Key: CONNECTORS-1533
>                 URL: https://issues.apache.org/jira/browse/CONNECTORS-1533
>             Project: ManifoldCF
>          Issue Type: Bug
>          Components: Lucene/SOLR connector
>    Affects Versions: ManifoldCF 2.11
>            Reporter: Julien Massiera
>            Assignee: Karl Wright
>            Priority: Major
>             Fix For: ManifoldCF 2.11
>
>         Attachments: 2018-09-23-012800.png, CONNECTORS-1533.patch
>
>
> The "r69acbd9 - Fix solr connector content deletion bug" has introduced 
> another bug : 
> It is now impossible to ingest documents into Solr 7.4.0, we obtain the 
> following error : Error from server at http://localhost:8983/solr/FileShare: 
> missing content stream
> The fact is, the requestWriter.getContentWriter(request) object is equal to 
> null only on commit requests. So the new lines of code introduced by the fix, 
> which are based on the test of this object, result in a null 
> Collection<ContentStream> streams object and so the update request is failing.
> Concerned class : 
> org.apache.manifoldcf.agents.output.solr.ModifiedHttpSolrClient



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to