Time to say: Thank you all for your great support!
-Andre
You need to use an untokenized field for facets.
At least 3 answers in 5 minutes... we should try synchronized swimming
;-)
-Yonik
Hi all,
I just installed the nightly build to try the Faceted Searching . After some
testing I discovered that some characters are missing in the result XML and
that fields with / chars are sometimes split into two entries.
Example:
int name=franc1/int should be France
int
: I just installed the nightly build to try the Faceted Searching . After
: some testing I discovered that some characters are missing in the result
: XML and that fields with / chars are sometimes split into two entries.
I believe what you are encountering is an issue of tokenization (or
You need to use an untokenized field for facets. I can see we're
going to get this question frequently now - it was mentioned earlier
today in fact. You can use a copyField that is untokenized such
that you can use one field for searching, and one for facets.
You are obviously using a
On Sep 13, 2006, at 9:37 PM, Chris Hostetter wrote:
http://www.nabble.com/Error-in-faceted-browsing-tf2267819.html
...i'll try to update the docs for facet.field to make this more
obvious.
Would it ever make sense to generate facets on a tokenized field?
Maybe the facet implementation
On 9/13/06, Erik Hatcher [EMAIL PROTECTED] wrote:
Would it ever make sense to generate facets on a tokenized field?
Maybe the facet implementation could throw an error if the field name
specified is tokenized?
I think it probably can make sense...
- finding top terms in a full-text field that
On 9/13/06, Erik Hatcher [EMAIL PROTECTED] wrote:
You need to use an untokenized field for facets.
At least 3 answers in 5 minutes... we should try synchronized swimming ;-)
-Yonik
