Hi
Just switched from Lucene 5.1 to Lucene 5.5 and noticed that
org.apache.lucene.search.CachingWrapperQuery has been deprecated.
Up until now I used that class to solve the following problem: I have a
query covering multiple fields. In the end, I have to give feedback on
which fields matched
7:07 PM, Otmar Caduff wrote:
> Hi
>
>
>
> Just switched from Lucene 5.1 to Lucene 5.5 and noticed that
> org.apache.lucene.search.CachingWrapperQuery has been deprecated.
>
>
>
> Up until now I used that class to solve the following problem: I have a
> query coveri
Hi all
In Lucene, I know of the possibility of Occur.SHOULD, Occur.MUST and the
“minimum should match” setting on the boolean query.
Now, when querying, I want to
- (1) match the documents which either contain all the terms of the query
(Occur.MUST for all terms would do that) or,
- (2) if all t
Hi,
I have an index with a single document with a field "field" and textual
content "johnny peters" and I am using
org.apache.lucene.queryparser.complexPhrase.ComplexPhraseQueryParser to
parse the query:
field: (john* peter)
When searching with this query, I am getting the document as expected.
; query?
>
> Ahmet
>
>
> On Tuesday, December 20, 2016 4:56 PM, Otmar Caduff
> wrote:
>
>
>
> Hi,
>
> I have an index with a single document with a field "field" and textual
> content "johnny peters" and I am using
> org.apache.lucene.query
Hi
Some days ago, I encountered some unexpected behaviour and filed the following
issue:
https://issues.apache.org/jira/browse/LUCENE-7650
No feedback yet. Does anybody know if such an issue will be fixed soon?
Otmar
-
To unsub
Dear committers
Recently I wanted to be able to extend wildcard queries over phrases.
To do so, I dived into ComplexPhraseQueryParser.
It turned out that making a small change to that class allows me to
achieve my goal.
Because I thought that change might help others, I opend a Jira issue
and at
