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

mosh edited comment on SOLR-12441 at 6/27/18 11:07 AM:
-------------------------------------------------------

Unless we find a better way, we might have to.
 Perhaps we could define in the schema that a specific field is a child key.
 That means that a nested JSON document is a child document if one of these 
cases is true:
 # The document has a unique Id key.
 # The document is specified as a child document in the collection's schema.

With Solr 8.0 around the corner, perhaps we could add something to specify that 
this is an Atomic update, separating such case from a childDoc? perhaps a 
prefix ("atomic"?) such as "atomicAdd" or "inPlaceAdd"?


was (Author: moshebla):
Unless we find a better way, we might have to.
 Perhaps we could define in the schema that a specific field is a child key.
 That means that a nested JSON document is a child document if one of these 
cases is true:
 # The document has a unique Id key.
 # The document is specified as a child document in the collection's schema.

With Solr 8.0 around the corner, perhaps we could add something to specify that 
this is an Atomic update?

> 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: 2h 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Reply via email to