Details
-
Sub-task
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
-
None
Description
A long standing pain point of the parent/child QParsers is the "all parents" bitmask/filter specified via the "which" and "of" params (respectively).
This is particularly tricky/painful to "get right" when dealing with multi-level nested documents...
- https://issues.apache.org/jira/browse/SOLR-14383?focusedCommentId=17166339&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17166339
- https://lists.apache.org/thread.html/r7633a366dd76e7ce9d98e6b9f2a65da8af8240e846f789d938c8113f%40%3Csolr-user.lucene.apache.org%3E
...and it's really hard to get right when the nested structure isn't 100% consistent among all docs:
- collections that mix docs w/o children and docs that have children.
- Ex: blog posts, some of which have child docs that are "comments", but some don't
- when some "types" of documents can exist at multiple levels:
- Ex: top level "product" documents, which may have 2 types of children: "skus" and "manuals", but "skus" may also have their own wku-specific child "manuals"
BUT! ... now that we have some semi-native support for the nest_path field, i think it may be possible to offer an "easier to use" variant syntax of the parent/child QParsers that directly depends on these fields. This new syntax should be optional – and purely syntactic sugar. "expert" users should be able to do all the same things using the existing syntax (possibly more efficiently depending on what invarients exist in their data model)
Attachments
Issue Links
- is related to
-
-
- Closed
-