: business needs. Our problem is that we have a catalog schema with
: products and skus, one to many. The most relevant content being indexed
: is at the product level, in the name and description fields. However we
: are interested in filtering by sku attributes, and in particular making
:
The separate sku do not become one long text string. They are separate
values in the same field. The relevance calculation is completely
separate per value.
The performance problem with the field collapsing patch is that it
does the same thing as a facet or sorting operation: it does a sweep
throu
Hi again, I'm gonna try this again with more focus this time :D
1) Ideally what we would like to do, is plug in an additional mechanism to
filter the initial result set, because we can't find a way to implement our
filtering needs as filter queries against a single index. We would want to do
t
