I'm currently drilling down adding a facet path, but I'd like to be able to
do the same as a NOT query. Is there any way to do an exclusion drill down
on a facet to exclude docs that match the facet while including all others?
Thanks
Interesting. Are there any examples of how to actually use
DiversifiedTopDocsCollector?
On Fri, Dec 2, 2016 at 8:53 AM Adrien Grand wrote:
> Maybe you could use DiversifiedTopDocsCollector?
> https://lucene.apache.org/core/6_2_0/misc/org/apache/lucene/search/DiversifiedTopDocsCollector.html
>
>
Hi,
you may also have a look at the implementation of the PKIndexSplitter, doing
exactly what you want (applying a FilterReader / FilterCodecReader that hides
documents matched by a query):
https://github.com/apache/lucene-solr/blob/master/lucene/misc/src/java/org/apache/lucene/index/PKIndexSpli
Do I get it right that you have a query that defines a set of visible
documents, and you want to make sure that your FilterReader only sees those
documents?
If this is the case, then you could use FixedBitSet.or to load the
Scorer.iterator() into a FixedBitSet, and then maintain two caches:
- one
Not part of Lucene, but take a look at LUCENE-5205 [1], which I actively
maintain on github [2].
And, you can integrate via maven [3]
See the jira issue for an overview of the query syntax, and let me know if you
have any questions.
[1] https://issues.apache.org/jira/browse/LUCENE-5205
[2] h
Hello,
You can check ComplexPhrase and Surround query parsers.
On Mon, Dec 5, 2016 at 8:12 AM, Yonghui Zhao wrote:
> It seems lucene query parser doesn't support SpanNearQuery.
> Is there any query parser supports SpanNearQuery?
>
--
Sincerely yours
Mikhail Khludnev
Hello Hendrik,
I lurked sources and find nothing better than copy a few pieces
from org.apache.lucene.search.MultiTermQueryConstantScoreWrapper and
especially
org.apache.lucene.search.MultiTermQueryConstantScoreWrapper.createWeight(...).new
ConstantScoreWeight() {...}.scorer(DocIdSet).
On Sun, De
Hi Mike,
Sorry for the delay.
For some use cases, Fields are implemented by numeric values, but distinct
values are not so big (<50 terms).
We have a Search GUI, where user can add criteria on predefined fields. For
those fields, where the number of terms is limited, then we proposed the
availa
