To allow deleting the document block all at once, here is another possibility:
In addDocuments() function, add an internal field, i.e.,
"_num_children_docs_", for the number of children documents. Since the
doc ID of all parent/children documents are consecutive, we can use
this internal field tog
I see. Probably assigning blockID is the most efficient way. Thanks.
On Sun, Mar 3, 2013 at 7:39 AM, Michael McCandless
wrote:
> IndexWriter doesn't track the blocks ... so you need to something yourself.
>
> One approach is to add a Field, eg blockID, with the same value (maybe
> the id of the p
IndexWriter doesn't track the blocks ... so you need to something yourself.
One approach is to add a Field, eg blockID, with the same value (maybe
the id of the parent doc) to parent and child docs, and then delete by
that.
You may also get away with just deleting the parent or just the
children,
Hello,
I understand BlockJoinQuery can be used to index nested documents with
some internal structure. And at indexing time, addDocuments is used to
create document blocks.
In case we would like to update some data fields, we have to delete
the old document block and add the updated block. How ca
