[
https://issues.apache.org/jira/browse/SOLR-12685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16603156#comment-16603156
]
David Smiley commented on SOLR-12685:
-------------------------------------
You make a good argument for consistency; I think we should keep the current
behavior (i.e. only get child documents if you ask).
Your new title of this issue seems to be conflated with SOLR-12638, and no
longer suggests this subsumes SOLR-9006. So it's pretty confusing what's going
on, to me. I think it's fine for SOLR-12638 to touch RTG code as its
implementation details; no need to have a separate issue unless you think it's
sufficiently distinct for whatever reason (e.g. if it accomplishes some other
useful benefit, _and_ there is work to do in SOLR-12638 that is separate and if
they could be committed separately without disrupting things). In light of
that, perhaps mark this issue closed?
> RTG should Support atomic updates of nested/child documents for
> nested-enabled schema
> -------------------------------------------------------------------------------------
>
> Key: SOLR-12685
> URL: https://issues.apache.org/jira/browse/SOLR-12685
> Project: Solr
> Issue Type: Sub-task
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: mosh
> Priority: Major
> Attachments: SOLR-12638-no-commit.patch
>
>
> Currently Solr's RealTimeGet component return the document if provided a
> docId when consulting the index. For AtomicUpdates for child documents, RTG
> should return the whole block when dealing with a nested schema.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
