[ 
https://issues.apache.org/jira/browse/SOLR-12298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

mosh updated SOLR-12298:
------------------------
    Description: 
Solr ought to have the ability to index deeply nested objects, while storing 
the original document hierarchy.
 Currently the client has to index the child document's full path and level to 
manually reconstruct the original document structure, since the children are 
flattened and returned in the reserved "__childDocuments__" key.

Ideally you could index a nested document, having Solr transparently add the 
required fields while providing a document transformer to rebuild the original 
document's hierarchy.

 

This issue is an umbrella issue for the particular tasks that will make it all 
happen – either subtasks or issue linking.

  was:
Solr ought to have the ability to index deeply nested objects, while storing 
the original document hierarchy.
Currently the client has to index the child document's full path and level to 
manually reconstruct the original document structure, since the children are 
flattened and returned in the reserved "_childDocuments_" key.

Ideally you could index a nested document, having Solr transparently add the 
required fields while providing a document transformer to rebuild the original 
document's hierarchy.

 

This issue is an umbrella issue for the particular tasks that will make it all 
happen – either subtasks or issue linking.


> Index Full nested document Hierarchy For Queries (umbrella issue)
> -----------------------------------------------------------------
>
>                 Key: SOLR-12298
>                 URL: https://issues.apache.org/jira/browse/SOLR-12298
>             Project: Solr
>          Issue Type: Improvement
>      Security Level: Public(Default Security Level. Issues are Public) 
>            Reporter: mosh
>            Priority: Major
>
> Solr ought to have the ability to index deeply nested objects, while storing 
> the original document hierarchy.
>  Currently the client has to index the child document's full path and level 
> to manually reconstruct the original document structure, since the children 
> are flattened and returned in the reserved "__childDocuments__" key.
> Ideally you could index a nested document, having Solr transparently add the 
> required fields while providing a document transformer to rebuild the 
> original document's hierarchy.
>  
> This issue is an umbrella issue for the particular tasks that will make it 
> all happen – either subtasks or issue linking.



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