On Jun 15, 2005, at 12:12 PM, Mike Barry wrote:
I have a situation where a query such as "climate control" is
returning
documents with the phrase "climate of control". (I'm using
QueryParser).
After searching, I found the similar issue on the mailing list from
Greg Robertson
with a patch
Hi all,
We are getting ready to implement our lucene search tools and want to
know if the following scenario is even possible :
The application user has a group and a role.
Document has name, author, body, and a list (of groups and roles it
is visible to), and a list of smart groups (dynami
I like this approach. This may be what I'm looking for.
Thanks JP!
-Jay
On 6/15/05, Robichaud, Jean-Philippe
<[EMAIL PROTECTED]> wrote:
>
> It may be simpler and more effective to use the Hits object and keep the
> number of time each host was actually "returned" to the user and skip it if
> the
It may be simpler and more effective to use the Hits object and keep the
number of time each host was actually "returned" to the user and skip it if
the limit has been reach. This way, if your users just look at the 10-20
highest hits, you will save you a lot of processing time, especially if you
Thanks Tony and Erik for the replies. The trick is we don't know the
hosts that will be returned in advance, we just don't want more than 3
from any one host. It's not unlike searching on Google where you might
see a link that says "More results from foo.com". We essentially want
to discard any res
The method Similarity.queryNorm() normalizes query term weights. To
disable this you could define it to return 1.0 in your own Similarity
implementation.
http://lucene.apache.org/java/docs/api/org/apache/lucene/search/Similarity.html#queryNorm(float)
Doug
Robichaud, Jean-Philippe wrote:
Ok,
I have a situation where a query such as "climate control" is returning
documents with the phrase "climate of control". (I'm using QueryParser).
After searching, I found the similar issue on the mailing list from
Greg Robertson
with a patch from Steve Rowe.
Looking at the source repository for
Ok, I know that usually, the scores returned by Lucene do not mean "really"
something. But in my case, it does, I play with the similarity and bla bla
bla... Now my concern is that the Query.setBoost() does not always seems to
affect the score. I've built a simple test (code completely at the e
