[
https://issues.apache.org/jira/browse/SOLR-3333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13248602#comment-13248602
]
Shawn Heisey commented on SOLR-3333:
------------------------------------
I never actually answered your first question. Yes, I do want most entries in
the filter cache to be usable for autowarming. Most users have relatively few
boolean clauses in their filter queries. Employees are the common exception.
We get a few hundred boolean clauses in ours. Plans are being discussed to
greatly reduce that, but I'm not sure we'll ever get away from it entirely.
> Create an option that allows a query to be cached, but not used for warming
> ---------------------------------------------------------------------------
>
> Key: SOLR-3333
> URL: https://issues.apache.org/jira/browse/SOLR-3333
> Project: Solr
> Issue Type: New Feature
> Affects Versions: 3.5, 4.0
> Reporter: Shawn Heisey
>
> The application that uses my Solr install builds complex filter queries for
> employees because they have access to everything, whereas most users have
> access to a small subset.
> Because of this, autowarming on the filterCache can take 30-60 seconds even
> though autoWarm is set to just 4 queries.
> If we had a way (probably a localparam) to tell Solr to not use those filters
> when autowarming, but to go ahead and put them in the filterCache and use
> them until there's a new commit, that would eliminate this problem.
> Employees might have their queries take longer, but regular users would not
> be affected.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
