On 3/12/26 16:02, Gus Heck wrote:
Coincidentally, I was just made aware of this ticket that may be of interest here: https://issues.apache.org/jira/browse/SOLR-14687 There is a PR now too: https://github.com/apache/solr/pull/4206
Skimming through the discussions, our use case does not involve either parent or child paths, it's simply the case of keeping the number of results down in the UI.
That is, if you have (e.g.) an atlas of maps, you want to return the atlas (parent) when the query hits a map (child) in it.
The other use case is support for compound data types like ordered lists or key-value dicts: say, you have a historic building that comes with a bunch of images: { "front view" : "img1.jpg", "E view" : "img2.jpg", ... } -- AFAIK this is not representable in the stock data types. I think having child objects as "first class citizens" would help a lot with this, but it's not obvious to me how paretPath/childPath would accomplish that.
Dima
