[
https://issues.apache.org/jira/browse/SOLR-12685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16587388#comment-16587388
]
mosh commented on SOLR-12685:
-----------------------------
I have started working on this,
and currently the biggest hold I have encountered is the lack of the ability
to set the return fields for the ChildDocTransformer, or a way to get the
document's _nest_path_(docValue) without having to build a new
SolrInputDocument, or a way to get a DocValue(__nest_path__) by docId.
The path of the parent which is updated is needed to get the document which is
to be changed by the atomic update in the block(nested SolrInputDocument).
e.g. when there's an atomic update
{code:javascript}
{"id": "2", "children": {"add": {"id":4, "test_s": "test"}}{code}
is made, and the doc with id:2 is itself a child doc of doc id:1, we need to
get the path of doc id:2, to add the new child doc to it.
I could upload a very rough no-commit patch, if needed.
> 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
