> You will need to write a custom analyzer. Don't worry, though it's
> quite straightforward. You will also need to write a Tokenizer, but
> Lucene helps you a lot here.
Wouldn't I achieve the same result if I index "time out" like "time_out",
using StandardAnalyzer and later if I search for
> When you are doing two searches are you searching for two different terms?
>
No, I am searching for the same term.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
What is the easyest way to eliminate duplicate documents if one is doing two searches
on the same index?
Have anybody done something similar?
t;searchable" (I need to
tokenize them like "man" "people" "time out" "sun").
Your solution isn't doing tokenizing, right?
Dragan Jotanovic
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
uld achieve this if I tokenize "time out" as one
token while idexing.
Maybe someone had similar problem? If someone knows how to handle this, please help me.
Dragan Jotanovic
>I do have one question. If you know the order of >documents to be
>retrieved, why use Lucene? Why not just display the >results to the user
>in your hand picked order?
I need a very fast search engine because I am working with thousends of
images. Lucine is providing me with that.
Does somebody
I have an index with data about images (those data are obtained from database). In
Document among other fields I have one field that I use for sorting. That field could
take 10 different values (1 to 10). I set boost for that field like following:
viewPriority:1^10
viewPriority:2^9
viewPri
