As Ameer mentioned use TextField to phrases.
Thanks
Sent from my iPhone
> On Oct 10, 2019, at 11:33 AM, Ameer Albahem wrote:
>
> A StrField field is not tokenized. So, do not expect "a b" to match "a a b".
> Lucene will generate a single term from "a b", and a single term from "a a
> b", so
A StrField field is not tokenized. So, do not expect "a b" to match "a a b".
Lucene will generate a single term from "a b", and a single term from "a a b",
so obviously, they do not match.
If you want to match these two texts, change the field to TextField and use the
appropriate analysis
1> Add =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
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
