[
https://issues.apache.org/jira/browse/SOLR-12685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16588379#comment-16588379
]
mosh commented on SOLR-12685:
-----------------------------
{quote}Is this a duplicate of SOLR-9006?{quote}
This ticket incorporates it, since it should return child docs from the
transaction log in addition to the index,
in case the document was not found there.
Quoting [~ariel_lieber...@hotmail.com] in SOLR-9006:
{quote}Therefore, I think the capability (e.g. additional flag) to get parent
with all its children is very important..{quote}
In my opinion adding extra flags only complicates this, and should instead
check if the schema is usable for child docs...
Perhaps there is a need though to only get that specific doc, and not the whole
block, even though the document is in the block, perhaps in place update(I am
not very familiar with those features, just to make sure)?
> 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
>
> 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
