when you say a security filter, are you asking if I can express my security constraint as a query? If that is the case then the answer is no. At this point I have a requirement to secure Terms (a nightmare I know). Our fallback is to aggregate the authorizations to a document level and secure the document which I think we wouldn't have to do anything to the caches but our customer has pushed back on this in the past.
On Tue, Aug 18, 2015 at 7:46 PM, Yonik Seeley <ysee...@gmail.com> wrote: > On Tue, Aug 18, 2015 at 7:11 PM, Jamie Johnson <jej2...@gmail.com> wrote: > > Yes, my use case is security. Basically I am executing queries with > > certain auths and when they are executed multiple times with differing > > auths I'm getting cached results. > > If it's just simple stuff like top N docs returned, can't you just use > a security filter? > > The queryResult cache uses both the main query and a list of filters > (and the sort order) for the cache key. > > -Yonik >
