[
https://issues.apache.org/jira/browse/SOLR-12441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16607315#comment-16607315
]
David Smiley commented on SOLR-12441:
-------------------------------------
This is debatable and I'm glad you asked because I'd like your input.
[~moshebla] and I are overall working to make nested docs in Solr much nicer,
under the umbrella SOLR-12298. We're going one piece at a time. This issue
here, SOLR-12441 and recent ones we're doing imply that the schema is
explicitly enabled for this new enhanced support for nested documents. That
means the schema needs to have certain special fields and configured in certain
ways. The nature of those fields, however, isn't completely nailed down yet.
Hopefully we can target this in 8.0, as it's a big deal. So my preference is
to delay ref guide documentation of this URP here right now. Stuff that _can_
be documented better in the ref guide that is part of the umbrella pertain to
attaching child documents under field names (versus stand-off anonymous
relationship). That aspect is complete, I think.
> Add deeply nested documents URP
> -------------------------------
>
> Key: SOLR-12441
> URL: https://issues.apache.org/jira/browse/SOLR-12441
> Project: Solr
> Issue Type: Sub-task
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: mosh
> Assignee: David Smiley
> Priority: Major
> Fix For: 7.5
>
> Time Spent: 7h 50m
> Remaining Estimate: 0h
>
> As discussed in
> [SOLR-12298|https://issues.apache.org/jira/browse/SOLR-12298], there ought to
> be an URP to add metadata fields to childDocuments in order to allow a
> transformer to rebuild the original document hierarchy.
> {quote}I propose we add the following fields:
> # __nestParent__
> # _nestLevel_
> # __nestPath__
> __nestParent__: This field wild will store the document's parent docId, to be
> used for building the whole hierarchy, using a new document transformer, as
> suggested by Jan on the mailing list.
> _nestLevel_: This field will store the level of the specified field in the
> document, using an int value. This field can be used for the parentFilter,
> eliminating the need to provide a parentFilter, which will be set by default
> as "_level_:queriedFieldLevel".
> _nestLevel_: This field will contain the full path, separated by a specific
> reserved char e.g., '.'
> for example: "first.second.third".
> This will enable users to search for a specific path, or provide a regular
> expression to search for fields sharing the same name in different levels of
> the document, filtering using the level key if needed.
> {quote}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
