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

Jason Gerlowski commented on SOLR-8808:
---------------------------------------

+1 for this JIRA.

SolrJ code tends to take a laissez-faire approach to validating inputs, which 
has a tendency for allowing odd errors to crop up down the line.  This is a 
good example of that.  Would love to see this get fixed here (and elsewhere in 
SolrJ at large, as a separate story).

Anyone see any downsides to fixing this that I might be missing?



> SolrJ deleteById causes missing content stream exception
> --------------------------------------------------------
>
>                 Key: SOLR-8808
>                 URL: https://issues.apache.org/jira/browse/SOLR-8808
>             Project: Solr
>          Issue Type: Bug
>          Components: SolrJ
>    Affects Versions: 5.5
>            Reporter: Markus Jelsma
>            Priority: Minor
>             Fix For: master, 6.1
>
>
> {code}
> client.deleteById(new ArrayList<String>()); 
> {code}
> Causes
> {code}
> org.apache.solr.client.solrj.impl.HttpSolrClient$RemoteSolrException: Error 
> from server at http://127.0.0.1:50083/collection1: Error from server at 
> http://127.0.0.1:50083/control_collection: missing content stream
>         at 
> __randomizedtesting.SeedInfo.seed([6C4973F1A077B797:65D362791DA8A1AD]:0)
>         at 
> org.apache.solr.client.solrj.impl.HttpSolrClient.executeMethod(HttpSolrClient.java:576)
>         at 
> org.apache.solr.client.solrj.impl.HttpSolrClient.request(HttpSolrClient.java:240)
>         at 
> org.apache.solr.client.solrj.impl.HttpSolrClient.request(HttpSolrClient.java:229)
>         at 
> org.apache.solr.client.solrj.SolrRequest.process(SolrRequest.java:149)
>         at org.apache.solr.client.solrj.SolrClient.commit(SolrClient.java:482)
>         at org.apache.solr.client.solrj.SolrClient.commit(SolrClient.java:463)
> {code}
> Although this is not a big issue, it had me puzzled for a while. A test 
> unrelated to one i was working on started sending empty deletes. Causing 
> above trace.
> Perhaps SolrJ should guard for empty input, just ignore and return.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Reply via email to