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
/core/8_1_1/core/org/apache/lucene/util/BitSet.html?is-external=true
per sub-reader."? If so, given the data above how do I properly create a
parent query?
> On July 3, 2019 at 10:30 AM Mikhail Khludnev mailto:m...@apache.org > wrote:
>
>
> On Wed, Jul 3, 2019
the block, why do we
need to provide a query for them?
> On July 3, 2019 at 10:52 AM ANDREI SOLODIN wrote:
>
>
> Thanks Mikhail.
>
>
> I read through the javadoc and thought I was satisfying all the
> preconditions. Obviously not :-) Is it this part that
figure out
> which "generation" or "level" of parent to select?
>
> On Wed, Jul 3, 2019 at 2:50 PM ANDREI SOLODIN wrote:
> >
> > After looking through the unit tests, I got it working. The problem was
> > that I thought the parent filter in the ToParent
Hello, I am also keenly interested in Lucene performance on NFS/EFS. I have an
extensive experience with a another (proprietory) search engine successfully
using NFS for indexing/search. In our case, the key has always been making sure
that a large portion of the index is in the host page cache,
