[jira] [Commented] (SOLR-3333) Create an option that allows a query to be cached, but not used for warming

["Shawn Heisey (Commented) (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SOLR-3333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13248292#comment-13248292 ] 

Shawn Heisey commented on SOLR-3333:
------------------------------------

I don't think I can implement this.  My knowledge of Solr internals simply isn't strong enough.

                
> 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-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org