[Xapian-tickets] [Xapian] #350: Stopping wildcard expansion at some point

[Xapian]

#350: Stopping wildcard expansion at some point
-------------------------+--------------------------------------------------
 Reporter:  asjo         |        Owner:  olly    
     Type:  enhancement  |       Status:  assigned
 Priority:  normal       |    Milestone:  1.1.1   
Component:  QueryParser  |      Version:          
 Severity:  normal       |   Resolution:          
 Keywords:               |    Blockedby:          
 Platform:  All          |     Blocking:          
-------------------------+--------------------------------------------------
Changes (by olly):

  * status:  new => assigned
  * milestone:  => 1.1.1


Old description:

> If there are many (many) terms with the same prefix and a wildcard search
> matching those is performed, the QueryParser tries to create a huge
> query, exhausting RAM even on reasonably sized machines (8GB).
>
> Attached is a patch that makes it possible to ask the QueryParser to
> throw an exception if a wildcard expands to more than a configurable
> number of terms.
>
> Some discussion on the mailinglist:
>
>  * http://thread.gmane.org/gmane.comp.search.xapian.general/7124

New description:

 If there are many (many) terms with the same prefix and a wildcard search
 matching those is performed, the !QueryParser tries to create a huge
 query, exhausting RAM even on reasonably sized machines (8GB).

 Attached is a patch that makes it possible to ask the !QueryParser to
 throw an exception if a wildcard expands to more than a configurable
 number of terms.

 Some discussion on the mailinglist:

  * http://thread.gmane.org/gmane.comp.search.xapian.general/7124

--

Comment:

 Adding to the 1.1.1 bucket...

-- 
Ticket URL: <http://trac.xapian.org/ticket/350#comment:1>
Xapian <http://xapian.org/>
Xapian