On Sat, Aug 30, 2014 at 4:25 AM, Alexander Klimetschek <[email protected]> wrote: > ...you can leverage some kind of caching though. In practice, if you have a > public site > with content that does not change permanently, the facet values are pretty > much > stable, and authorization shouldn't cost much....
Yes, I think it's very rare to require facets to be immediately up to date after content changes, updating them (or the related caches) asynchronously with low priority should be good enough for the large majority of cases. So maybe the facet indexes and caches can be handled differently than "primary" queries, with more lenient update latency requirements. -Bertrand
