[
https://issues.apache.org/jira/browse/SOLR-12441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16536510#comment-16536510
]
David Smiley commented on SOLR-12441:
-------------------------------------
I'm still not clear why the right-hand side pound is necessary; I think the
left-hand (leading) pound is sufficient. e.g. this is fine:
{{child#0/grandchild#0}}
{quote}Do you mean to strip childNum off the _NEST_PATH field?
{quote}
Yes – of the _indexed_ form *but not* the _stored_ form. The indexed form would
look like {{child/grandchild}}. For an exact match (no all ancestors or all
descendents), we can index using KeywordTokenizerFactory. In your Peyton
Manning example, this would mean your child filter would be {{_NEST_PATH_:from
AND name:Peyton*}}. See PathHierarchyTokenizerFactoryTest and the descendents
vs ancestors distinction as well via two differently indexed fields for
use-cases involving descendents and ancestors if we need that. With some
tricks we could use one field if we need all 3 (exact, descendants, ancestors).
> 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
> Time Spent: 6h 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
