lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jan Høydahl (JIRA) <>
Subject [jira] [Commented] (SOLR-12441) Add deeply nested documents URP
Date Wed, 04 Jul 2018 20:01:00 GMT


Jan Høydahl commented on SOLR-12441:

Why would nest_path need to be unique? Guess there could be a use case for listing all child
docs having the same path too.

> Add deeply nested documents URP
> -------------------------------
>                 Key: SOLR-12441
>                 URL:
>             Project: Solr
>          Issue Type: Sub-task
>      Security Level: Public(Default Security Level. Issues are Public) 
>            Reporter: mosh
>            Assignee: David Smiley
>            Priority: Major
>          Time Spent: 4h 40m
>  Remaining Estimate: 0h
> As discussed in [SOLR-12298|], there
ought to be an URP to add metadata fields to childDocuments in order to allow a transformer
to rebuild the original document hierarchy.
> {quote}I propose we add the following fields:
>  # __nestParent__
>  # _nestLevel_
>  # __nestPath__
> __nestParent__: This field wild will store the document's parent docId, to be used for
building the whole hierarchy, using a new document transformer, as suggested by Jan on the
mailing list.
> _nestLevel_: This field will store the level of the specified field in the document,
using an int value. This field can be used for the parentFilter, eliminating the need to provide
a parentFilter, which will be set by default as "_level_:queriedFieldLevel".
> _nestLevel_: This field will contain the full path, separated by a specific reserved
char e.g., '.'
>  for example: "first.second.third".
>  This will enable users to search for a specific path, or provide a regular expression
to search for fields sharing the same name in different levels of the document, filtering
using the level key if needed.
> {quote}

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message