: Our users can blow up the parser without special characters. : : AND THE BAND PLAYED ON : TO HAVE AND HAVE NOT
Grrr... yeah, i'd forgotten about that problem. I was hopping LUCENE-682 could solve that (by "unregistering" AND/OR/NOT as operators) but that issue fairly dead in the water since the performance differnece wsa fairly significant. DisMaxQueryParser should really just have it's own grammer instead of the hacks i put in to subclass QueryParser. : We have auto-complete on titles, so the there are plenty : of chances to inadvertently use special characters: : : Romeo + Juliet : Airplane! : Shrek (Widescreen) : : We also have people type "--" for a dash in titles. Only the '+' and '-' characters are special in those examples ... the others will be treated as literal characters by dismax. but like i said we could patch dismax to have an option containing the list of characters to auto-escape that would default to the current hardcoded list ... for your use case you could have all the special characters (including '+' and '-') .. still wouldn't solve your quote problem though -- that's where we'd need hooks for subclasses to override the quote striping. -Hoss
