lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "mosh (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (SOLR-12441) Add deeply nested documents URP
Date Wed, 04 Jul 2018 13:21:00 GMT

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

mosh edited comment on SOLR-12441 at 7/4/18 1:20 PM:
-----------------------------------------------------

I have been thinking about a special case where a child documents within an array has other
children.
 Perhaps we should keep inside the _NEST_PATH_ field the child documents' index in the hierarchy.
e.g.
{code:javascript}
{"_NEST_PATH_": "book/pages[3]/footnote"}{code}
Or perhaps it should be:
{code}{"_NEST_PATH_": "book[0]/pages[3]/footnote[0]"}{code}
WDYT?


was (Author: moshebla):
I have been thinking about a special case where a child documents within an array has other
children.
 Perhaps we should keep inside the _NEST_PATH_ field the child documents' index in the hierarchy.
e.g.
{code:javascript}
{"_NEST_PATH_": "book/pages[3]/footnote"}{code}
Or perhaps it should be:
{"_NEST_PATH_": "book[0]/pages[3]/footnote[0]"}{code}
WDYT?

> 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: 4h 40m
>  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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message