lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Smiley (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SOLR-12298) Index Full nested document Hierarchy For Queries (umbrella issue)
Date Thu, 03 May 2018 15:06:00 GMT

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

David Smiley commented on SOLR-12298:
-------------------------------------

It'll be exciting to see Solr's nested document support get improved!

* You said the JSON loader could have changes but then wouldn't that limit the benefit to
only that update method?  Why not an URP instead?
* Will {{\_path\_}} have a chain of uniqueKey IDs from parent to child?  You didn't specify
what it is.  Or, after re-examining Anshum's LSR presentation you referenced, is this a list
of the name of the entity type at each level (e.g. "post.comment.reply.keywords" etc.)?  If
it is some sort of entity name, then this name needs to be put into each child document so
that this type path can be constructed?

Perhaps these special fields should all start with "nest" so as to clearly distinguish these
for support of nested documents?  e.g. nestParent, nestLevel, nestPath  (with leading &
trailing underscores; escaping in JIRA is a pain :-) )

> 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-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message