On Jul 26, 2005, at 3:04 AM, Paul Elschot wrote:
+(spanNear([FULLTEXT:cat, FULLTEXT:dog, FULLTEXT:bird], 1, true)
spanNear([FULLTEXT:horse, FULLTEXT:cow, FULLTEXT:pig], 1, true)
spanNear([FULLTEXT:snake, FULLTEXT:camel], 0, true)) +(FULLTEXT:zebra
FULLTEXT:insect spanNear([FULLTEXT:feline, FULLTEXT:goat], 0, true))
Reformatted to show the structure:
+(spanNear([FULLTEXT:cat, FULLTEXT:dog, FULLTEXT:bird], 1, true)
spanNear([FULLTEXT:horse, FULLTEXT:cow, FULLTEXT:pig], 1, true)
spanNear([FULLTEXT:snake, FULLTEXT:camel], 0, true)
)
+(FULLTEXT:zebra
FULLTEXT:insect
spanNear([FULLTEXT:feline, FULLTEXT:goat], 0, true)
)
The top level ConjunctionScorer nicely shows up in the traceback.
Quite a sophisticated query mixing BooleanQuery and SpanNearQuery
clauses.
Let me know if there is other information I can provide, or other
variants of BooleanScorer2 I can try.
Thanks,
Erik
java.lang.ArrayIndexOutOfBoundsException: More matchers (4) than non
prohibited scorers (3).
The DisjunctionSumScorer for one of the two 3 way queries is adding
too many matchers.
Added 4 for doc nr 4930.
0 required scorers.
3 optional scorers.
0 prohibited scorers.
This is consistent with the query.
Could you keep this index around for later tests?
Absolutely. I've got it ready to test anytime.
Erik
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
