Hmmm... Seems like a lot of work to be done. I will try these options and
update.
Thanks a lot.
Best.
--
View this message in context:
http://n3.nabble.com/Problem-with-search-tp717137p719604.html
Sent from the Lucene - Java Users mailing list archive at Nabble.com.
--
I don't know if that proposal is the most efficient one, but you can try it.
In general, what you're looking for is a GROUP BY Bill-Id feature and then
select the most recent one, right? Only you don't need all the Versions of
the same Bill, and therefore you can hold the most recent Version-Id onl
Also, please note that I thought about it and realized that I mispoke
when I sent out my original suggestion. You don't want an untokenized
field in your case, you want an unstemmed one instead.
This will allow you to get the functionality you are looking for.. at
least I believe so ^^
Anyh
Thanks for the reply.
I will try to add an other data field.
I thought about this solution but i was not very sure. I thought that was an
easier solution to do that...
best regards
Renou
2008/6/26 Matthew Hall <[EMAIL PROTECTED]>:
> You could also add another data field to the index, with an
You could also add another data field to the index, with an untokenized
version of your data, and then use a multifield query to go against both
the stemmed and exact match parts of your search at the same time.
This is a technique I've used quite often on my project with various
different req
The way I've solved this is to index the stemmed *and* a special
token at the same position (see Synonym Analyzer). The From your
example, say you're indexing progresser. You'd go ahead and index the
stemmed version , "progress", AND you'd also index "progresser$"
at the same offset. Now, when you
