: extraction algorithm, etc.) So, for a product with 50% of #00, and 20%
: of #99, I'll have to fill the remaining three fields with some dummy
: values. Otherwise, Lucene seems to score it higher than products that also
: have 50% of #00, but more than 20% of some other colors. Since
>
> can you you explain exactly how you are indexing the data and what your
> query looks like?
>
I used the same field name (color), not 10 different names (c0 - c9).
So the index fields look like (50% #00, 20% #99):
color: #00
color: #00
color: #00
color: #00
color: #000
'k. see SOLR-368.
--cw
On 9/28/07, Yonik Seeley <[EMAIL PROTECTED]> wrote:
>
> On 9/28/07, Clay Webster <[EMAIL PROTECTED]> wrote:
> > i'm late for dinner out, so i'm just attaching it here.
>
> Most attachments are stripped :-)
>
> -Yonik
>
: I used the same field name (color), not 10 different names (c0 - c9).
ah .. got it. then what you are probably seeing is because of length
normalization, if you use omitNorms="true" then it shouldn't matter.
(i don't know why i suggested a seperate field for each 10% block ... i'm
sure i ha
: Is it possible to use faceting to not only get the facet count but also the
: top-n documents for every facet
: directly? If not, how hard would it be to implement this as an extension?
not hard ... a custom request handler could subclass
StandardRequestHandler, call super.handleRequest, and t
