is empty.
hacker win7
hackersw...@gmail.com
> On Sep 28, 2020, at 21:06, Adrien Grand wrote:
>
> What are you storing in your points? If you are storing numbers, I wonder if
> a better approach to this problem might be to start leveraging
> IndexOrDocValuesQuery and scorerSuppl
Is there any reasons for this why PointInsetQuery return NO_MORE_DOCS instead
of NULL while NULL can terminate early.
hacker win7
hackersw...@gmail.com
> On Sep 29, 2020, at 11:59, hacker win7 wrote:
>
> Thanks Adrien Grand
>
> We store long numbers in our points, in our
() can return null, as the comment says: “This method may
return null if no documents were added to this”
I’m not sure why this changes.
hacker win7
hackersw...@gmail.com
> On Sep 28, 2020, at 21:06, Adrien Grand wrote:
>
> What are you storing in your points? If you are storing n
lt.bitSet is null, there is no specific point value at
all then return null ->
This will terminate early in the BooleanWeight.scoreSupplier() because subScore
is null and the boolean clause is required
The following SubQuery2, SubQuery3, SubQuery4 …. Need not to call
scorerSupplier() to build sco
