: > Hmmm, i see ... well the easiest way to go is not to worry about it when : > parsing the query, when you go to compute facets for all hte fields you : > tink might be useful, you'll see that only one value for "brand" matches, : > and you can just skip it.
: I would think that this is not the best option in terms of performance. It's not as bad as it sounds assuming a finite number of facets and enough ram that they all can fit into the filterCache. I have a handler that computes thousands of facet constraint counts, and i don't worry about wether or not any of the existing filter queries makes them unneccessary. since they're all cached, it's just quick set intersections. -Hoss
