I have a similar interest in specifying a custom scoring strategy. I
previously posted about it under the subject "Scoring a document
(count?)" on 7/27/06. In brief, I want a documents score to be a count
of term matches. This is nearly identical to a SQL count()
functionality.
If you are able
uld return the raw tf as a
score, as an exercise. It is not a product level implementation of
course, but if you think this will help you (?) I can share the code.
(Would have responded sooner, for my working computer went off for a few
days with a fan error...:-).
Regards,
Doron
"Russell M.
ormance considerations, depending on the
star| volume
of the data...
Regards,
Doron
"Russell M. Allen" <[EMAIL PROTECTED]> wrote on 27/07/2006
09:02:46:
> I am curious about the potential use of document scoring as a means to
> extract additional data from an index. Spe
7;ve got the stored value of the "horror"
field to tell you how many movies they've been in.
: Date: Thu, 27 Jul 2006 12:02:46 -0400
: From: Russell M. Allen <[EMAIL PROTECTED]>
: Reply-To: java-user@lucene.apache.org
: To: java-user@lucene.apache.org
: Subject: Scoring a
You should build your own performance test cases to see what works for your
data. That being said, here are some numbers from a similar test I ran:
I did the following:
1) run a single term query which resulted in about half of the total set of
documents being returned. (~36,000)
2) built a Bo
I am curious about the potential use of document scoring as a means to
extract additional data from an index. Specifically, I would like the
score to be a count of how many times a particular field matched a set
of terms.
For example, I am indexing movie-stars (Each document is a movie-star).
A
: 1) colorzing your mail doesn't play nicely with the mailing list ...
: sending "diffs" is the prefered way to show potential changes to the
code.
So I discovered on sending the message. :)
: 2) assuming i understand what it is you've changed, you've "worked
arround" the TooManyClausesException
We recently ran into an issue while executing a simple prefix search
"name:b*", which results in a BooleanQuery$TooManyClauses exception. At
first I found it odd that a single clause query was causing this, but as
I dug into the code I found where the PrefixQuery rewrites itself as a
BooleanQuery.
