Ugh, that sucks. I think wildcards & fuzzy queries should be configurable options of edismax. It strikes me as a bug that the wildcard & fuzzy operators were applied to all words. I don't think it's up for the client application layer to do something about it this since; this is a Solr problem. Did you file a bug Erick?
~ David Smiley Erick Erickson wrote: > > Sorry if this double-posts, but gmail is being wonky... > > I saw a situation recently where query strings with isolated > meta-characters were going to edismax with unfortunate results. For > instance: > > blah blah * blah blah > > or > > blah blah ~ blah blah > > edismax happily spreads these across all of the fields leading > to...er...interesting behavior, and 5+ minute query responses. > > Should we consider dis-allowing any of these? Or is the best response > that they should have Solr locked down and take care of this at the > app level if they care? > > I suspect the right answer is the latter but thought I'd throw it out > for discussion. > > Erick > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > ----- Author: https://www.packtpub.com/solr-1-4-enterprise-search-server/book -- View this message in context: http://lucene.472066.n3.nabble.com/edismax-and-wildcards-tp3269153p3269918.html Sent from the Lucene - Java Developer mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
