lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jamie Johnson <>
Subject Re: Disable caching
Date Mon, 24 Aug 2015 17:13:26 GMT
I ran into another issue that I am having issue running to ground.  My
implementation on Solr 4.x worked as I expected but trying to migrate this
to Solr 5.x it looks like some of the faceting is delegated to
DocValuesFacets which ultimately caches things at a field level in the
FieldCache.DEFAULT cache.  I don't see anyway to override this cache or
augment the key in anyway, am I missing an extension point here?  Is there
another approach I should be taking in this case?

On Wed, Aug 19, 2015 at 9:08 AM, Jamie Johnson <> wrote:

> This was my original thought.  We already have the thread local so should
> be straight fwd to just wrap the Field name and use that as the key.  Again
> thanks, I really appreciate the feedback
> On Aug 19, 2015 8:12 AM, "Yonik Seeley" <> wrote:
>> On Tue, Aug 18, 2015 at 10:58 PM, Jamie Johnson <>
>> wrote:
>> > I think I have things setup correctly, I have a custom
>> > QParserPlugin building a custom query that wraps the query built from
>> the
>> > base parser and stores the user who is executing the query.  I've added
>> the
>> > username to the hashCode and equals checks so I think everything is
>> setup
>> > properly.  I ran a quick test and it definitely looks like my items are
>> > being cached now per user, which is really great.
>> >
>> > The outage that I'm running into now is the FieldValueCache doesn't take
>> > into account the query, so the FieldValueCache is built for user a and
>> then
>> > reused for user b, which is an issue for me.  In short I'm back to my
>> > NoOpCache for FieldValues.  It's great that I'm in a better spot for the
>> > others, but is there anything that can be done with FieldValues to take
>> > into account the requesting user?
>> I guess a cache implementation that gets the user through a thread
>> local and either wraps the original key with an object containing the
>> user, or delegates to a per-user cache underneath.
>> -Yonik

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message