[
https://issues.apache.org/jira/browse/SOLR-3333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13248579#comment-13248579
]
Shawn Heisey commented on SOLR-3333:
------------------------------------
I would like to have our application code tag those nasty employee filters with
something that makes them ineligible for autowarming, but still eligible for
caching, which would keep them around until the next commit. I am pretty sure
our code is capable of knowing that the user is a special user, typically admin
or system.
An update cycle runs once a minute for the index as a whole, but changes are
tracked on a per-shard basis. Commits on each shard are only done if something
on that particular shard actually changes. The large shards where this is a
problem typically go several minutes between commits, and that might extend to
an hour or more.
I will talk to our developers about using the cache=false localparam for now,
but I am hoping for the ability to use the cache for those nasty filters but
not include them for warming. Having recently toyed with the cache code
(SOLR-2906), I know this may not be trivial.
> 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
