[ 
https://issues.apache.org/jira/browse/SOLR-12440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16499439#comment-16499439
 ] 

Cassandra Targett commented on SOLR-12440:
------------------------------------------

Is this a (possibly accidental) duplicate of SOLR-12441?

> Add deeply nested documents URP
> -------------------------------
>
>                 Key: SOLR-12440
>                 URL: https://issues.apache.org/jira/browse/SOLR-12440
>             Project: Solr
>          Issue Type: New Feature
>      Security Level: Public(Default Security Level. Issues are Public) 
>         Environment: As stated in SOLR-12298, there ought to be an URP to add 
> metadata fields to solr child documents, so the full original document 
> hierarchy can be rebuilt using a transformer.
> {quote}1. __nestParent__
>  2. __nestLevel__
>  3. __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".
> __nestPath__: 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}
>            Reporter: mosh
>            Priority: Major
>




--
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

Reply via email to