Mailing-List: contact java-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-user@lucene.apache.org
Received-SPF: pass (asf.osuosl.org: domain of markrmiller@gmail.com designates
 64.233.162.197 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:user-agent:mime-version:to:subject:references:in-reply-to:content-type:content-transfer-encoding;
        b=ERKylsDyrnjrDDtvYDOg4Ii+WUeOBJe9XcddPm80Pg3yh2ZK4DSzL7eKVhgOgtpAlkAoYSQqPNwvZx31o8/EExGNWT71H3oqEPUSvfS7FyYd7N7yZB4uh4knFYtPMVWzTFCOMq+QBNzzNE0vIICqSo1E6d7vlQ1verGItJEqDNk=
Message-ID: <44F82084.3000000@gmail.com>
Date: Fri, 01 Sep 2006 07:59:00 -0400
From: Mark Miller <markrmiller@gmail.com>
User-Agent: Thunderbird 1.5.0.5 (Windows/20060719)
MIME-Version: 1.0
To: java-user@lucene.apache.org
Subject: Re: SpanRegex speed
References: <6016090.post@talk.nabble.com>
	 <Pine.LNX.4.58.0608281149320.10385@hal.rescomp.berkeley.edu>
	 <6035831.post@talk.nabble.com>
	 <Pine.LNX.4.58.0608291132220.3758@hal.rescomp.berkeley.edu>
	 <6057151.post@talk.nabble.com>
	 <Pine.LNX.4.58.0608301137380.4558@hal.rescomp.berkeley.edu>
	 <44F60D80.1070802@gmail.com>
	 <9A767EEF-1DF0-41A6-8991-28516D912ADF@ehatchersolutions.com>
	 <44F64698.3070800@gmail.com>
 <359a92830608310627r5a463c04kbbe6fcd7841465ff@mail.gmail.com>
In-Reply-To: <359a92830608310627r5a463c04kbbe6fcd7841465ff@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Erick Erickson wrote:
> Let me chime in here on a different note.... before you get happy with
> wildcard queries, take a look at the thread "I just don't get 
> wildcards at
> all". There is lots of good info that Erik, Chris and Otis provided me.
>
> The danger with prefixquery and wildcard query is that they will throw
> TooManyClauses exceptions when you start matching a number of terms (the
> default is 1024, although you can make this much bigger if memory 
> allows).
> If you're aware of this and it is and will be OK in your app, ignore 
> this.
> But if your index is going to grow significantly, this is a real 
> problem. I
> went with implementing filters with WildCardTermEnum (you could also use
> RegexTermEnum) for the wildcard portions of my query. Which has 
> interesting
> implications for spans, we elected to say spans didn't work with 
> wildcards.
>
> Anyway, as I said, if you're aware of the TooManyClauses issue and are 
> sure
> it doesn't matter, ignore me. After all, everybody else does <G>.....
>
>
> Best
> Erick
>
>
>
> On 8/30/06, Mark Miller <markrmiller@gmail.com> wrote:
>>
>> Ignore that last question. I see that you said prefix wildcard query and
>> not wildcard query. A quick look at the code seems to show it grabbing a
>> prefix as well.
>>
>> Do you think one would be any faster than the other? Should I used
>> Wildcardqueries outside of spanqueries and the regexquery inside
>> spanqueries or use regex both places?
>>
>> - Mark
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
>> For additional commands, e-mail: java-user-help@lucene.apache.org
>>
>>
>
Thanks a lot for the info Eric. Good stuff to know for sure.
I guess the real question I have been trying to spit out is this:
Is a span version of any of these searches--fuzzy, wildcard, 
etc--inherently slower than their non-span brothers. If they have the 
same limitations and speeds then that is all I am looking for.

P.S.
I realize I have been screwing up the threading by replying when 
starting a new topic. I have been alerted and will stop this pernicious 
activity.

- Mark

---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-user-help@lucene.apache.org