I've implemented a custom Query whose responsibilities are as follows.
First, using an instance of a PointValues.IntersectVisitor classifying
documents as hit or not using a plong value. Secondly, calculating custom
scores using another document field, specified in the mapping as plongs.
The later
Recently I've implemented a custom Query that in turn scores documents
using a custom Scorer implementation using a long primitive point values.
The associated field is multi valued and has doc values enabled. For
retrieving these multi valued longs I've used LeafReader.document() within
the Scorer
ow stored fields, misusage of docvalues APIs (those are iterators, too)
> or other problems.
>
> Uwe
>
> -
> Uwe Schindler
> Achterdiek 19, D-28357 Bremen
> http://www.thetaphi.de
> eMail: u...@thetaphi.de
>
> > -Original Message-
> > From: Do
.thetaphi.de
> eMail: u...@thetaphi.de
>
> > -Original Message-
> > From: Dominik Safaric [mailto:dominiksafa...@gmail.com]
> > Sent: Wednesday, October 11, 2017 1:39 PM
> > To: java-user@lucene.apache.org
> > Subject: Re: Lucene 7.x custom Scorer on po
Hi,
I am intending to implement a custom Query using Lucene 6.x and due to the lack
of documentation concerned with a particular topic I have the following
questions.
The query is expected to implement a two-phase search, in the sense that during
the first run it matches documents according t
h[ing]
> documents according to criteria X". Can you give an example?
>
> Le ven. 9 févr. 2018 à 14:47, Dominik Safaric a
> écrit :
>
> > Hi,
> >
> > I am intending to implement a custom Query using Lucene 6.x and due to
> the
> > lack of document
ild();
>
> It's not clear to me why you need to retain order: the order of your values
> should not matter?
>
> Le lun. 12 févr. 2018 à 11:23, Dominik Safaric a
> écrit :
>
>> In particular, I have a document schema as follows:
>>
>> {
>> "
Hi,
As I'm in the process of implementing a custom Lucene scorer, I'd like to
know how to read using the LeafReader a multi-value keyword value.
In particular, the multi-value keyword field I'm storing consists of 6
values (subject to change though), and I'd like to retrieve those values
using th
> So, can doc values be persisted with order of values, not document id? This
> should be fast in sort scenario that the values are pre-ordered instead of
> scan/sort at runtime.
No, unfortunately doc values cannot be persisted in order. Lucene stores this
values internally as a DocValuesType.
