[
https://issues.apache.org/jira/browse/SOLR-12441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16523300#comment-16523300
]
mosh edited comment on SOLR-12441 at 6/26/18 6:54 AM:
------------------------------------------------------
{quote}Can you please provide further justification for _nestLevel_ like a more
fleshed out scenario?{quote}
After sleeping on this it seems like this can be solved using a simple regex.
This field was to be used in case the user only wants to query certain levels
of the nested document, but this can be filtered using a regex checking for the
number of split char('.') in the field name. This can be easily done using a
transformer.
The thing is we would need to query the whole block instead of including
another filter in the query itself to pick only the wanted children. Perhaps
this is a better approach in terms of index weight saving. What do you think
[~dsmiley]?
was (Author: moshebla):
{quote}Can you please provide further justification for _nestLevel_ like a more
fleshed out scenario?{quote}
After sleeping on this it seems like this can be solved using a simple regex.
This field was to be used in case the user only wants to query certain levels
of the nested document, but this can be filtered using a regex checking for the
number of split char('.') in the field name. This can be easily done using a
transformer.
I will work on a commit eliminating this field.
> 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
> Time Spent: 1h 10m
> 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]
