: Also, it would be nice to make this a (non static) method of Query, and, I
: think, also of Weight and Scorer (Weight would "like-inherit" that property
: from its Query, and Scorer from its Weight). The default would be
as i recall, the staticness was so that people writing apps could garuntee
Chris Hostetter <[EMAIL PROTECTED]> wrote on 19/04/2007 16:01:53:
>
> : With this committed it also makes sense to deprecate the
setUseScorer14()
> : method and the corresponding get...() method. If you want a patch for
that,
> : I'll gladly provide one.
>
> i haven't really been able to follow th
: With this committed it also makes sense to deprecate the setUseScorer14()
: method and the corresponding get...() method. If you want a patch for that,
: I'll gladly provide one.
i haven't really been able to follow this issue as much as i would like,
but docs now sometimes coming out of order
[
https://issues.apache.org/jira/browse/LUCENE-847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12490192
]
Steven Parkes commented on LUCENE-847:
--
Here are some numbers comparing the load performance for the factored vs
Hi there,
I am new to Lucene and would appreciate any help on this. Thank you in
advance.
I want the order of the search results based on the keywords mentioned in
the meta information of the document. For example, if I have two very
similar documents first.htm and second.htm, first.htm has keywor
OK, I see it now. I was thinking I was scoring that individual term
at that position, but if I had read the Scorer documentation better
instead of assuming I knew what it meant I wouldn't have had this
problem, as it clearly says it advances the document.
I will try to fix it by the end of
Grant Ingersoll wrote:
OK, I need to take a step back, Michael, b/c I thought I understood
your original comment, but I went to make the change and am no longer
sure.
By "first term position" are you referring to multiple terms per
position or do you mean the same term in different position
