[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=16540915#comment-16540915 ]

Hoss Man commented on SOLR-12441:
---------------------------------

I'm late to the party, and haven't tried to catch up on the issue too much (stoked you guys are working on this though!) but ... i have a small bit of bike-shedding to ask about...

why are these new field names upper case?  wouldn't lower case be more consistent with the existing special fields like {{\_root\_}} and {{\_version\_}} ?

{noformat}
+  public static final String NEST_PARENT_FIELD_NAME = "_NEST_PARENT_";
+  public static final String NEST_PATH_FIELD_NAME = "_NEST_PATH_";
{noformat}

(i couldn't find any comment that seemed to mention the upper casing being a conscious choice compared to the original {{\_nestParent\_}} etc... -- although +1 to removing the camel case either way)

> 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
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]