lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "mosh (JIRA)" <>
Subject [jira] [Commented] (SOLR-5211) updating parent as childless makes old children orphans
Date Thu, 17 Jan 2019 05:14:00 GMT


mosh commented on SOLR-5211:

{quote}What if we delete the complete block and create the block again and add again via UpdateChainProcessorFactory.
In that way, will update only those fields/docs what we want to and put the block back in
Have you had a look at SOLR-12638?
 It allows deleting and adding child docs as an atomic update.
{quote}That's one workaround I am planning to try (on 7.5) – delete the parent & children,
then re-add. Unfortunately, I believe this will take two calls.{quote}
I am not sure whether [SOLR-12638|] will make
it to Solr 7.

> updating parent as childless makes old children orphans
> -------------------------------------------------------
>                 Key: SOLR-5211
>                 URL:
>             Project: Solr
>          Issue Type: Sub-task
>          Components: update
>    Affects Versions: 4.5, 6.0
>            Reporter: Mikhail Khludnev
>            Assignee: David Smiley
>            Priority: Blocker
>             Fix For: 8.0
>         Attachments: SOLR-5211.patch, SOLR-5211.patch, SOLR-5211.patch, SOLR-5211.patch,
>          Time Spent: 3h 40m
>  Remaining Estimate: 0h
> if I have parent with children in the index, I can send update omitting children. as
a result old children become orphaned. 
> I suppose separate \_root_ fields makes much trouble. I propose to extend notion of uniqueKey,
and let it spans across blocks that makes updates unambiguous.  
> WDYT? Do you like to see a test proves this issue?

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message