[
https://issues.apache.org/jira/browse/SOLR-12441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16542277#comment-16542277
]
Hoss Man commented on SOLR-12441:
---------------------------------
{quote}Oops; you're right Hoss. I'll change them to camelCase.
{quote}
I'm *NOT* suggesting camel case... just lowercase...
{noformat}
public static final String NEST_PARENT_FIELD_NAME = "_nest_parent_";
public static final String NEST_PATH_FIELD_NAME = "_nest_path_";
{noformat}
(we have not had any camel case fields (of fieldTypes) in the {{_default}}
configset up to now, i don't see any reason to change that)
bq. 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. ...
I don't have strong feelings ... my gut would say: leave it out of {{_default}}
for at least a few (minor) releases, let people who want it add it, see how
well it works in real world usecases and if there are any serious design/API
flaws we want to revisit before including it by default. But that's not based
on any specific concerns about this code/api/idea -- it's just my general
cautiousness about changing defaults :)
> 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: [email protected]
For additional commands, e-mail: [email protected]
