Removed attachment proves that ComplexPhraseQuery toString() is just
misguiding.
On Tue, Oct 22, 2019 at 5:51 PM Shifflett, David [USA] <
shifflett_da...@bah.com> wrote:
> I saw the changes in the diff.
> But without looking into the test, I am asking to confirm if it
> matches my conditions:
> 1
I saw the changes in the diff.
But without looking into the test, I am asking to confirm if it
matches my conditions:
1) Uses a StandardAnalyzer
2) Does the actual query.toString() return lowercase J and S
David Shifflett
On 10/22/19, 10:44 AM, "Mikhail Khludnev" wrote:
On Tue, Oct 22, 20
On Tue, Oct 22, 2019 at 5:26 PM Shifflett, David [USA] <
shifflett_da...@bah.com> wrote:
> Mikhail,
>
> Thanks for running those tests.
> I haven’t looked into the test, but can you confirm it uses an analyzer
> with the lowercase filter?
>
Look at his diff. It's a diff on test not a test
-ch
Mikhail,
Thanks for running those tests.
I haven’t looked into the test, but can you confirm it uses an analyzer with
the lowercase filter?
Also can you confirm whether the actual query being used contains upper or
lower case J and S (in you John Smith case)
Apologizes on the 'content:foo'.
I c
Hello,
I wonder how it come up with this particular field :
content:foo
Anyway I added some uppercase in the test and it passed despite of it
diff --git
a/lucene/queryparser/src/test/org/apache/lucene/queryparser/complexPhrase/TestComplexPhraseQuery.java
b/lucene/queryparser/src/test/org/apache/lu
