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/12/12 14:21:58 UTC
[jira] [Comment Edited] (SOLR-4587) Implement Saved Searches a la
ElasticSearch Percolator
[ https://issues.apache.org/jira/browse/SOLR-4587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15741981#comment-15741981 ]
Joel Bernstein edited comment on SOLR-4587 at 12/12/16 2:21 PM:
----------------------------------------------------------------
Hi,
I also saw your post on the reference guide. Let's discuss this a little bit on this ticket and then we can move to users list to continue the discussion.
1) About SOLR-8709. The issue here is that it's possible that an out of order version number could persist across commits. But I've tested this in many different scenarios and have never been able to make it happen. In all my testing I've never once seen the topic() function fail to retrieve all documents from the topic. Also Solr is not a transactiional system so data loss in general is possible. So I'm not sure the chance of data loss in this scenario is any worse the chance of data loss in Solr in general.
2) In Solr 6.3 we now have an executor:
https://cwiki.apache.org/confluence/display/solr/Streaming+Expressions#StreamingExpressions-executor
This allows you to shuffle topics to worker nodes and execute them in parallel. This should scale fairly well.
was (Author: joel.bernstein):
Hi,
I also saw your post on the reference guide. Let's discuss this a little bit on this ticket because and then we can move to users list to continue the discussion.
1) About SOLR-8709. The issue here is that it's possible that an out of order version number could persist across commits. But I've tested this in many different scenarios and have never been able to make it happen. In all my testing I've never once seen the topic() function fail to retrieve all documents from the topic. Also Solr is not a transactiional system so data loss in general is possible. So I'm not sure the chance of data loss in this scenario is any worse the chance of data loss in Solr in general.
2) In Solr 6.3 we now have an executor:
https://cwiki.apache.org/confluence/display/solr/Streaming+Expressions#StreamingExpressions-executor
This allows you to shuffle topics to worker nodes and execute them in parallel. This should scale fairly well.
> Implement Saved Searches a la ElasticSearch Percolator
> ------------------------------------------------------
>
> Key: SOLR-4587
> URL: https://issues.apache.org/jira/browse/SOLR-4587
> Project: Solr
> Issue Type: New Feature
> Components: SearchComponents - other, SolrCloud
> Reporter: Otis Gospodnetic
> Fix For: 6.0
>
>
> Use Lucene MemoryIndex for this.
--
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