Hmmm, I looked at this a bit more, and I don't think we can legitimately call this a bug. The exact same thing happens with non-edismax. That is, with a default field of "text", entering nonsense * silliness parses to
text:nonsens text:* text:silli Doing the same thing with a minimal edismax (qf of text and features) produces: +((title:nonsens | text:nonsens) (title:* | text:*) (title:silli | text:silli)) After all, the asterisk #is# just a token. And we do accept things like field:* So this seems consistent. And nonsense ~ silliness parses to +((title:nonsense~2.0 | text:nonsense~2.0) (title:silli | text:silli)) So I think GIGO is accurate here.... Erick On Tue, Sep 6, 2011 at 6:10 PM, Chris Hostetter <[email protected]> wrote: > > : GIGO is a valid response... > > I don't think GIGO is a valid attidude for a parser who'se whole purpose > is to accept anything an end user might through at it and "try to do it's > best" > > I agree with David: I think it's a bug that 0 length prefix/wildcard > queries are accepted by default with no config option to disable them. > > (FWIW: this kind of scneerio is exactly the type of thing i was > worried about i fought to not map "dismax"=>ExtendedDisMasQParser in 3.x) > > : >> 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. > > > -Hoss > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
