You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Joel Bernstein (JIRA)" <ji...@apache.org> on 2016/02/21 18:46:18 UTC

[jira] [Updated] (SOLR-8709) Account for out-of-order version numbers in the TopicStream

     [ https://issues.apache.org/jira/browse/SOLR-8709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Joel Bernstein updated SOLR-8709:
---------------------------------
    Summary: Account for out-of-order version numbers in the TopicStream  (was: Account for out of order version number is TopicStream)

> Account for out-of-order version numbers in the TopicStream
> -----------------------------------------------------------
>
>                 Key: SOLR-8709
>                 URL: https://issues.apache.org/jira/browse/SOLR-8709
>             Project: Solr
>          Issue Type: Bug
>            Reporter: Joel Bernstein
>
> Currently the TopicStream can miss documents if version numbers are received out-of-order. The TopicStream sorts on version number so it will only miss out-of-order versions that span commit boundaries.
> In order to resolve this issue we can adopt an approach that keeps a set of the last N version numbers sent in memory. As the documents are scanned we can check for documents within this time window that do not appear in the sent set. These documents can then be sent.



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

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