[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.2.x   
Component:  QueryParser  |     Version:          
 Severity:  normal       |    Keywords:          
Blockedby:               |    Platform:  All     
 Blocking:               |  
-------------------------+--------------------------------------------------

Comment(by richard):

 Just done a brief read-through of the patch - it looks pretty reasonable,
 though in
 xapian-core/queryparser/queryparser_internal.h I think the
 max_wildcard_expansion member should be initialised in the constructor,
 rather than assigned to.  ie:
 {{{
 default_op(Query::OP_OR), errmsg(NULL): max_wildcard_expansion(0) { }
 }}}

 The general functionality of this seems useful - though perhaps it should
 be a query-wide setting: the exception would be raised if a query would
 consist of more than the specified number of terms.  This would catch
 cases where a query contained multiple wildcards, each individual wildcard
 being composed of sufficiently few terms.

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