A thought - would you (or the project lead;-) consider limiting the
'wildcard expansion'?
Assuming a query like:
( uni* near(5) science )
I.e. match docs with any word with prefix "uni" that spans no further than
5 from the word "science". Assume current lexicon has M (say 1200) words
st
I'm almost entirely certain that any value I choose for setMaxClauseCount is
going to be wrong, but I might give it a try.
Erick
On 8/2/06, Paul Elschot <[EMAIL PROTECTED]> wrote:
On Wednesday 02 August 2006 17:29, Erick Erickson wrote:
> I'm back, with another flavor of wildcards. What direct
On Wednesday 02 August 2006 17:29, Erick Erickson wrote:
> I'm back, with another flavor of wildcards. What direction would you point a
> poor boy who's project lead wants wildcard queries and spans? Here's the
> problem
>
> I cannot use any of the classes that throw a "TooManyClauses" excepti
Hey! I'm actually looking all on my own. Anyway, 2 gives me
TooManyClauses. It looks like what I want is to use
IndexReader.termPositions to aggregate the offsets of all the wildcard terms
on a per-document basis, then walk the lists for proximity. Something
like...
for each wildcard term wt
fo
Well, I can't do 2 TooManyClauses again. Should have realized that the
terms are assembled independently
Erick
On 8/2/06, Erick Erickson <[EMAIL PROTECTED]> wrote:
I'm back, with another flavor of wildcards. What direction would you point
a poor boy who's project lead wants wildcard queri
I'm back, with another flavor of wildcards. What direction would you point a
poor boy who's project lead wants wildcard queries and spans? Here's the
problem
I cannot use any of the classes that throw a "TooManyClauses" exception (e.g.
SpanRegexQuery or SpanNearQuery with, say WildCardQuery).
