[
https://issues.apache.org/jira/browse/SOLR-12630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16573303#comment-16573303
]
David Smiley commented on SOLR-12630:
-------------------------------------
{quote}Perhaps using the nested update URP we could add the needed metadata
field(ROOT, _nest_path, _nest_parent)
{quote}
_From_ where? Oh; perhaps if it's an _update_ to an existing child doc, then we
could fetch the same metadata fields from that document? (if so this
underscores the need to use docValues to store that information, e.g. nest path
& nest parent ID & root)
New children won't have metadata that can be accessed in the existing index.
Perhaps a special field provided with a new document could point to its parent
and the label/relationship to that parent. Then this special field is removed
in the URP as its use is transient. Hmmm; maybe we should do away with the
child index number appended to the _nest_path_ field. I don't think we actually
need this digit? Maintaining it would be problematic with ad-hoc addition of
docs.
I think the schema would need a setting to indicate if the collection has
strict "block" nested docs, or wether it may be ad-hoc nested docs, or if there
are no nested docs at all (3-way toggle). With such a mechanism, fields like
"_root_" and others needn't be explicitly defined; they can be considered
implementation details of Solr's nested docs. It's not clear to me how your
suggestion of a field type would be used to make the distinction.
Before proceeding in this direction on the above aspects, it'd be good to
consider what an implementation-neutral query might look like. It would not
mention \{!join} or \{!child} or \{!parent}. Or alternatively, maybe
child|parent might be made aware of the aforementioned setting to "do the right
thing".
> Query children without using block join
> ---------------------------------------
>
> Key: SOLR-12630
> URL: https://issues.apache.org/jira/browse/SOLR-12630
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: mosh
> Priority: Major
>
> Currently work is being put into Solr to support nested document hierarchies,
> keeping the original relation between parent and child docs
> ([SOLR-12298|https://issues.apache.org/jira/browse/SOLR-12298],
> [SOLR-12441|https://issues.apache.org/jira/browse/SOLR-12441]). Currently the
> only way to query child documents is using BlockJoin. I was thinking perhaps
> we could introduce a way to query documents that are not indexed in the same
> block with a different transformer, or perhaps add this feature to the
> ChildDocTransformer.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
