lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "mosh (JIRA)" <>
Subject [jira] [Commented] (SOLR-12638) Support atomic updates of nested/child documents for nested-enabled schema
Date Wed, 01 May 2019 09:05:00 GMT


mosh commented on SOLR-12638:

{quote}Oh, I didn't know this or forgot. Ugh; I wish this weren't so. Since _route_ is a required
parameter for this feature, is the stored/docValue of _root_ actually truly necessary? Hmm;
do we at least throw an error if this is neglected when a user tries to do a partial update
to a child doc?
I'd like to move the discussion concerning the point [~dsmiley] raised(quoted above) from
[PR #405|] to this Jira

Should getting this to work without _root_ as stored be the main focus from now on?

> Support atomic updates of nested/child documents for nested-enabled schema
> --------------------------------------------------------------------------
>                 Key: SOLR-12638
>                 URL:
>             Project: Solr
>          Issue Type: Sub-task
>      Security Level: Public(Default Security Level. Issues are Public) 
>            Reporter: mosh
>            Assignee: David Smiley
>            Priority: Major
>             Fix For: 8.1
>         Attachments: SOLR-12638-delete-old-block-no-commit.patch, SOLR-12638-nocommit.patch,
SOLR-12638.patch, SOLR-12638.patch
>          Time Spent: 16h 50m
>  Remaining Estimate: 0h
> I have been toying with the thought of using this transformer in conjunction with NestedUpdateProcessor
and AtomicUpdate to allow SOLR to completely re-index the entire nested structure. This is
just a thought, I am still thinking about implementation details. Hopefully I will be able
to post a more concrete proposal soon.

This message was sent by Atlassian JIRA

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

View raw message