copyField it to an analyzed field will do the trick.
-Original message-
From: j
Sent: Sun 15-08-2010 20:30
To: solr-user@lucene.apache.org;
Subject: Re: uniqueKey and custom fieldType
Hi Erick, thanks- your explanation makes sense. But how then, do I
make my unique field useful in
Hi Erick, thanks- your explanation makes sense. But how then, do I
make my unique field useful in terms of searching. If I have a unique
column id with value:
sometexthere-1234567
and want it match the query '1234567', I need to use an analyzer to
split up the parts around the hyphen/dash. I gues
The short answer is that unique keys should be s single
term. String types are guaranteed to be single, since they
aren't analyzed. Your SplitUpStuff type *does* analyze
terms, and can make multiple tokens out of single strings
via WordDelimterFactory.
A common error when thinking about the "strin
I guess another way to pose the question is- what could cause
id to no longer be respected?
The last chance I made since I noticed the problem of non-unique docs
was by changing field "title" from "string" to "SplitUpStuff". But I
dont understand how that could affect the uniqueness of a differ
In order to make even a guess, we'd have to see your new
field type. Particularly its field definitions and the analysis
chain...
Best
Erick
On Fri, Aug 13, 2010 at 5:16 PM, j wrote:
> Does fieldType have any effect on the thing that I specify should be
> unique?
>
> uniqueKey has been working
