[
https://issues.apache.org/jira/browse/SOLR-12685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16601227#comment-16601227
]
David Smiley commented on SOLR-12685:
-------------------------------------
I think I see what's going on. This is a bit tricky. ChildDocTransformer
_does_ use the IndexSearcher so should declare itself as doing so (as you
pointed out). But it's only there to return child docs. If the parent doc is
in the update log, then it's children ought to be there too (it's a requirement
of nested docs after all), and in that event we actually don't need the child
doc transformer since the child docs will already be exactly where they need to
be in-place.
Perhaps the use of ChildDocTransformer should become automatic in RTG, thus RTG
can know when it's needed or not? Hmmm. I'll think about this some more; I
have to go for the day.
> RTG should return the whole block if schema is nested
> -----------------------------------------------------
>
> 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]
