[
https://issues.apache.org/jira/browse/SOLR-1990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12886422#action_12886422
]
ofer fort commented on SOLR-1990:
---------------------------------
Each document has it's own id.
The deleted document is not one of the added ones. It was added a while ago
and if my application realizes it is not relevant anymore, it will delete
it.
ב-08/07/2010, בשעה 21:47, "Yonik Seeley (JIRA)" <j...@apache.org> כתב/ה:
[
https://issues.apache.org/jira/browse/SOLR-1990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12886404#action_12886404]
Yonik Seeley commented on SOLR-1990:
------------------------------------
Is this behavior by design?
If you do an add followed by a delete of the same document, one would
normally expect that the document would be deleted. Without ordering
things, you can't really guarantee that though.
Of course the same problem exists if you add multiple documents with the
same id - you don't know which will end up winning by being last.
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.
> 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
