[jira] [Commented] (SOLR-12441) Add deeply nested documents URP

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view

[jira] [Commented] (SOLR-12441) Add deeply nested documents URP

JIRA jira@apache.org

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

David Smiley commented on SOLR-12441:

Oops; you're right Hoss.  I'll change them to camelCase.

I'd like your opinion on if/where/how this URP (and fields) might be incorporated into the default URP chain and default schema for the fields.  Note that the factory will detect the schema doesn't even have these fields and then pass through to the next URP, so it's low-overhead for those that don't have the fields.  I think it's critical I get another committer's explicit blessing on changing the default URP chain or schema so here I am asking you.

> Add deeply nested documents URP
> -------------------------------
>                 Key: SOLR-12441
>                 URL: https://issues.apache.org/jira/browse/SOLR-12441
>             Project: Solr
>          Issue Type: Sub-task
>      Security Level: Public(Default Security Level. Issues are Public)
>            Reporter: mosh
>            Assignee: David Smiley
>            Priority: Major
>             Fix For: 7.5
>          Time Spent: 7.5h
>  Remaining Estimate: 0h
> As discussed in [SOLR-12298|https://issues.apache.org/jira/browse/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: [hidden email]
For additional commands, e-mail: [hidden email]