[
https://issues.apache.org/jira/browse/SOLR-1990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12886371#action_12886371
]
Mark Miller commented on SOLR-1990:
-----------------------------------
Nice catch - is this causing you a particular problem?
Looks like if you submit a delete in a long line of adds, rather than putting
the delete into the request queue, it's going to block and wait for all the
previous doc adds to finish, then process the delete, then continue processing
docs.
Could always check for a delete query or delete id(s), but I wonder if there is
a better way to just check if the request is a commit or optimize rather than
checking everything else.
> blockUntilFinished() is called in StreamingUpdateSolrServer when deleing by id
> ------------------------------------------------------------------------------
>
> Key: SOLR-1990
> URL: https://issues.apache.org/jira/browse/SOLR-1990
> Project: Solr
> Issue Type: Bug
> Components: clients - java
> Affects Versions: 1.4.1
> Reporter: ofer fort
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> in the StreamingUpdateSolrServer .request() it identifies a commit/optimize
> request by having no document, but also the delete doesn't have a docuemnt.
> // this happens for commit...
> if( req.getDocuments()==null || req.getDocuments().isEmpty() ) {
> blockUntilFinished();
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
