So I dug into this a bit further, and find it happens with the stock
Lucene query as well, in 4.10.2. I looked at the code on trunk, and I
don't think the situation is different there. Basically if you delete a
parent document, orphaning some child document(s) and then merge, the
TPBJQuery fa
I've run into an exception, and I'm trying to understand whether it is
something that can just happen if the index doesn't conform to the
expectations of the TPBJQ, or if I've somehow messed things up in my
extension of that query.
The exception I'm seeing is in BlockJoinScorer.nextDoc(). It'
