You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Erick Erickson (JIRA)" <ji...@apache.org> on 2017/10/17 20:53:00 UTC
[jira] [Commented] (SOLR-11502) Query Elevate Component lazy
evaluation of queries
[ https://issues.apache.org/jira/browse/SOLR-11502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16208315#comment-16208315 ]
Erick Erickson commented on SOLR-11502:
---------------------------------------
Hmmm, what about another cache in solrconfig.xml? Seems like a fine thing for a cache as it could be limited by the number of entries. QEC was never envisioned as having 10,000 entries in the first place so how much memory used wasn't really part of the thinking at the time.
All the plumbing is in place, including a regeneration option to autowarm the N most recent QEC queries......
> Query Elevate Component lazy evaluation of queries
> --------------------------------------------------
>
> Key: SOLR-11502
> URL: https://issues.apache.org/jira/browse/SOLR-11502
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Components: query parsers, SearchComponents - other
> Affects Versions: 6.6.1, 7.1
> Reporter: Robert Lucarini
>
> Whenever a new searcher is opened, _all_ of the Query Elevate queries are run through the query parser and the results stored. So say you have 10,000 entries. The autowarming takes however long it takes to process 10,000 queries. It would help if there was an option to run the elevate query at query time instead of during autowarming.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org