Hi,-
does it matter which field is added first into index when multi field
Lucene is used?
does that make difference at search time like if it matches first and
second field (which are fuzzy queries and AND-mandatory search term) and
ignore third and fourth mandatory (AND) fields (search te
Hi there,
I was talking with Varun at Berlin Buzzwords a couple of weeks ago about
storing and retrieving Lucene indexes in S3, and realized that "uploading a
Lucene directory to the cloud and downloading it on other machines" is a
pretty common problem and one that's surprisingly easy to do poorl
Well for one thing, you might have other documents in the index that
are neither parents nor children (in this particular relation). Also,
consider a nested hierarchy - how can we automatically figure out
which "generation" or "level" of parent to select?
On Wed, Jul 3, 2019 at 2:50 PM ANDREI SOLO
After looking through the unit tests, I got it working. The problem was that I
thought the parent filter in the ToParentBlockJoinQuery can be used to select a
subset of parents. It appears that the parent filter must select ALL parents,
not a subset. This is not explained in the javadoc. If you
Thanks Mikhail.
I read through the javadoc and thought I was satisfying all the preconditions.
Obviously not :-) Is it this part that am I getting wrong: "At search time you
provide a Filter identifying the parents, however this Filter must provide an
BitSet
https://lucene.apache.org/core/8_1
On Wed, Jul 3, 2019 at 6:11 PM ANDREI SOLODIN wrote:
>
> This returns "id3", which is unexpected.
>
> Please check ToPBJQ javadoc. It's absolutely expected.
--
Sincerely yours
Mikhail Khludnev
Hello, I am trying to understand the requirements for properly using the
index-time join. In my use case, I am trying to model a 1-N relationship where
parent document could have 0-N child documents. For now I am keeping my data
very simple where each child has a single field. So my data right n
