You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@solr.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2021/06/12 18:49:00 UTC

[jira] [Commented] (SOLR-15044) Update JSON syntax: detect nested documents via schema

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

ASF subversion and git services commented on SOLR-15044:
--------------------------------------------------------

Commit 5a9a34daedb34cb5fc5dc6f8c5c40a734bb7dacb in solr's branch refs/heads/main from David Smiley
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=5a9a34d ]

SOLR-15044: JSON Loading: nested docs don't need ID (#143)

When indexing nested docs via JSON, it is no longer necessary to provide child doc IDs.
This was already working for XML & "javabin"/SolrJ.
Previously, omitting the ID would be confused for a partial/atomic update.

> Update JSON syntax: detect nested documents via schema
> ------------------------------------------------------
>
>                 Key: SOLR-15044
>                 URL: https://issues.apache.org/jira/browse/SOLR-15044
>             Project: Solr
>          Issue Type: Improvement
>            Reporter: David Smiley
>            Assignee: David Smiley
>            Priority: Major
>              Labels: NestedDocuments
>             Fix For: main (9.0)
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> When sending JSON formatted documents to Solr, particularly to /update/json/commands instead of /update/json/docs (those are API v2 paths), it tries to differentiate between wether a nested structure is either a nested document or an atomic update -- it's rather ambiguous.  Presently the logic is simply checking for the presence of an "id" but it may not be there (it is auto-computed when absent later).  It ought to simply look in the schema to see if the field exists or not.  If it doesn't, then it can't be an atomic update, thus treat it as a nested document.
> This was raised [on this comment in another JIRA issue|https://issues.apache.org/jira/browse/SOLR-12362?focusedCommentId=16526338&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16526338].



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@solr.apache.org
For additional commands, e-mail: issues-help@solr.apache.org