[
https://issues.apache.org/jira/browse/SOLR-4587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14199868#comment-14199868
]
Steve Davids commented on SOLR-4587:
------------------------------------
I don't think Luwak is really an implementation of this particular feature. It
does perform percolating functionality but as a stand-alone library which isn't
integrated into Solr. May I suggest that we take a stab at this without waiting
around for Luwak since the implementation is dependent on LUCENE-2878 which
seems to keep stalling over and over again. The initial approach can take the
naive loop across all queries for each document request and at a later point
the Luwak approach can be incorporated to provide some nice optimizations. Here
are some initial thoughts on acceptance criteria / what can be done to
incorporate this functionality into solr:
# Able to register a query within a separate Solr core
#* Should take advantage of Solr's sharding ability in Solr Cloud
#* This can piggy-back off of the standard SolrInputDocument semantics with
adding/deleting to perform query registration/deregistration.
#* Schema would define various fields for the stored query: q, fq, defType, etc.
# Able to specify which query parser should be used when matching docs
(persisted w/ query)
# Able to specify the other core that the document should be profiled against
(this can be at request time if you would like to profile against multiple
shards)
#* Allows the profiling to know the fields, analysis chain, etc
# Should allow queries to be cached in RAM so they don't need to be re-parsed
continually
# Custom response handler (perhaps a subclass of the search handler) should
make a distributed request to all shards to gather all matching query profile
ids and return to the client.
This is one of those features that would provide a lot of value to users and
would be fantastic if we can get incorporated sooner rather than later.
> 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: Trunk
>
>
> Use Lucene MemoryIndex for this.
--
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
