> Hey Ken,
> Thanks for your reply.
> When I wrote '5|6' I ment that this is a multiValued field with two
> values
> '5' and '6', rather than the literal string '5|6' (and any Tokenizer).
> Does
> your reply still holds? That is, are multiValued fields dependent on
> the
> notion of tokenization t
Hey Ken,
Thanks for your reply.
When I wrote '5|6' I ment that this is a multiValued field with two values
'5' and '6', rather than the literal string '5|6' (and any Tokenizer). Does
your reply still holds? That is, are multiValued fields dependent on the
notion of tokenization to such a degree so
> Hey,
> I have a field defined as such:
>
> stored="false"
> multiValued="true" />
>
> with the string type defined as:
>
> omitNorms="true"/>
>
> When I try using some query-time boost parameters using the bq on
> values of
> this field it seems to behave
> strangely in case of documents actua
Hey,
I have a field defined as such:
with the string type defined as:
When I try using some query-time boost parameters using the bq on values of
this field it seems to behave
strangely in case of documents actually having multiple values:
If i'd do a boost for a particular value ( "site_id
