1> Add &debug=query to the query and look at the parsed query returned. That’ll tell you a _lot_ about this kind of question.
2> look at the analysis page of the admin UI for the core and see how your field definition handles the tokens once they’re through <1>. Best, Erick > On Oct 10, 2019, at 11:18 AM, Jochen Barth <jpunktba...@gmail.com> wrote: > > Dear reader, > > I'm trying to test lucene 8.2.0 as key-value store; > > I know that there are specialized ones like lmdb etc... > > As key I have a StringField, keys can contain space(s), e. g. "a b". I know I > should use TermQuery. > > But I've been playing with classic QueryParser, which does not match the > indexed keys, > > not with »a backslash space b« > > nor with »quote a space b quote«. > > Now the funny part: The StandardQueryParser does work when querying "a b". It > does not match an additional key "a a b", so StandardQueryParser seems not to > do a phrase query despite both query parsers refer to the same syntax > description. > > Does StandardQueryParser takes field type into account when building the > query? > > Kind regards, Jochen > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org > For additional commands, e-mail: java-user-h...@lucene.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org For additional commands, e-mail: java-user-h...@lucene.apache.org
