Mailing-List: contact solr-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: solr-user@lucene.apache.org
MIME-Version: 1.0
In-Reply-To: <CAEFAe-GqvJNKYhFt_f_UnJkDoztu8L=hFKnzVevmc8NCBx6W8g@mail.gmail.com>
References: <CAEFAe-GqvJNKYhFt_f_UnJkDoztu8L=hFKnzVevmc8NCBx6W8g@mail.gmail.com>
From: Mikhail Khludnev <mkhl@apache.org>
Date: Sun, 4 Sep 2016 08:43:02 +0300
Message-ID: <CAF8TkC7ygW-VaFvCAUJNUWYOR_kVtWtnUnK=546Pew+MpbRhdg@mail.gmail.com>
Subject: Re: Nested documents: deleting the whole subtree
To: solr-user <solr-user@lucene.apache.org>
Content-Type: multipart/alternative; boundary=94eb2c07e8067028a9053ba8094c
archived-at: Sun, 04 Sep 2016 05:43:06 -0000

--94eb2c07e8067028a9053ba8094c
Content-Type: text/plain; charset=UTF-8

Hello Alex,
Internally, _root_ field is assigned across whole block. You can use it in
deleteByQuery. The value for this field is equal to parent's uniqueKey.

On Sun, Sep 4, 2016 at 5:51 AM, Alexandre Rafalovitch <arafalov@gmail.com>
wrote:

> Hello,
>
> If I am correct, deleting parent document still keeps the child
> documents in the index. Which means they now have dangling _root_
> references and what not.
>
> What's the easiest delete command to take out the parent and all its
> multilevel children, when I find the parents themselves with a query?
>
> So far, I got:
> (+type:release +release_name:"6.1.0") {!child
> of=type:release}release_name:"6.1.0"
>
> Is there a better way I missed?
>
> Regards,
>    Alex.
> P.s. Interestingly, the above query will still match children after
> the parent record is still gone. Until the merge/optimize anyway.
> Which shows that the deleted record filtering happens after all the
> matching, not just parent's matching.
>
> ----
> Newsletter and resources for Solr beginners and intermediates:
> http://www.solr-start.com/
>


-- 
Sincerely yours
Mikhail Khludnev

--94eb2c07e8067028a9053ba8094c--