[jira] [Commented] (SOLR-12298) Index Full nested document Hierarchy For Queries (umbrella issue)
[ https://issues.apache.org/jira/browse/SOLR-12298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17190530#comment-17190530 ] David Smiley commented on SOLR-12298: - > Question on this work: if a child document is stored in a field "foobar", > must that field be present in schema? No, it should not. > if one document has one child and another two with the same name, the > resulting Json (or SolrJ!) structure will be inconsistent and cause parsing > issues. Hmmm; that could be a limitation. Though a reasonable one I think always use an array if there may be more than one for that named child relation. > 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 >Reporter: mosh >Assignee: David Smiley >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > 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 (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
[jira] [Commented] (SOLR-12298) Index Full nested document Hierarchy For Queries (umbrella issue)
[ https://issues.apache.org/jira/browse/SOLR-12298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17183605#comment-17183605 ] Alexandre Rafalovitch commented on SOLR-12298: -- Question on this work: if a child document is stored in a field "foobar", must that field be present in schema? What type? And should its cardinality be respected when the query response is reconstructed? Because at the moment, the ChildDocTransformer looks at actual children counts instead of field definition and therefore if one document has one child and another two with the same name, the resulting Json (or SolrJ!) structure will be inconsistent and cause parsing issues. > 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 >Reporter: mosh >Assignee: David Smiley >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > 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 (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
