[GitHub] [druid] cheddar commented on issue #11836: Broker cannot use distributed cache to bypass historical querying for cached segment results

[GitBox <gi...@apache.org>]

cheddar commented on issue #11836:
URL: https://github.com/apache/druid/issues/11836#issuecomment-951362719


   Yeah, that change is definitely a breach of contract.  The design of the cache is to allow the broker to load results for a segment and then not send the query anymore for that segment.  This design can be both good and bad, but that's how it works.  The adjustment to the cache key from the other change breaks that and should probably be reverted (or put behind a non-default configuration)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For additional commands, e-mail: commits-help@druid.apache.org