Ha! I need to get used to the fact that 2.9 is out there already :)
Thanks mark for the addition.
simon
On Mon, Sep 28, 2009 at 11:18 PM, Mark Miller wrote:
> Though in 2.9 this is not much of a concern - the multi term queries are
> smart - if it matches few enough terms it will rewrite to a c
Though in 2.9 this is not much of a concern - the multi term queries
are smart - if it matches few enough terms it will rewrite to a
constant score booleanquery - if it matches a lot of terms it will
rewrite to a constantscore query - using a filter underneath. So
maxclause issues should no
Depending on your usecase you might want to use the PrefixFilter
instead of PrefixQuery which can be way more efficient than a query.
With a filter you have the possibility to cache it very easily and you
are not exposed to issued related to the length of the prefix. If you
have a very short prefix
John Seer wrote:
>
> Hello,
>
> Is there any benefit of using one or other for "start with query"?
>
> Which one is faster?
>
>
> Regards
>
It seems that you've answered your own question. If you want a "start with
query", this is exactly what a PrefixQuery is for. WildcardQuery gives yo
John Seer wrote:
> Hello,
>
> Is there any benefit of using one or other for "start with query"?
>
> Which one is faster?
>
>
> Regards
>
Prefix query is a bit more efficient - not sure what it turns into
realworld, but prefix just checks if the term's start with the prefix -
wildcard has a bi
