On Thursday 06 October 2005 22:46, Hoss Man (JIRA) wrote:
> [ http://issues.apache.org/jira/browse/
LUCENE-395?page=comments#action_12331531 ]
>
> Hoss Man commented on LUCENE-395:
> -
>
> I freely admit that I didn't give a lot of thought to incrimenting maxC
[
http://issues.apache.org/jira/browse/LUCENE-395?page=comments#action_12331531 ]
Hoss Man commented on LUCENE-395:
-
I freely admit that I didn't give a lot of thought to incrimenting maxCoord. I
did it only because if I didn't, coordinator.coordFactor() g
[
http://issues.apache.org/jira/browse/LUCENE-395?page=comments#action_12331519 ]
paul.elschot commented on LUCENE-395:
-
The patch applies cleanly and all tests pass including the new
TestBooleanMinShouldMatch.
The code to tranform the optional scorers
On Oct 6, 2005, at 8:28 AM, Ahmed El-dawy wrote:
Thanks for your help.
I used PhraseQuery to boost close terms. I think of an idea for sop
words but I don't know, if it has any drawbacks. I can index any dummy
Token in place of all stop words. This token will never be searched
but it will be cou
Thanks for your help.
I used PhraseQuery to boost close terms. I think of an idea for sop
words but I don't know, if it has any drawbacks. I can index any dummy
Token in place of all stop words. This token will never be searched
but it will be counted as a Token and will make a space between words.
When i am indexing a document which i already have indexed, it is creating a
different index for that. Therefore when i am going to search for a particular
field. it is showing the result for these two documents.
Now my problem is that how to control that repetition of data
Hoping for your h
