[ 
https://issues.apache.org/jira/browse/SOLR-15064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jan Høydahl updated SOLR-15064:
-------------------------------
    Environment:     (was: Updating to make a blocker for 9.0 because I 
_really_ want to remove the 9.0 hack RE {{\_route_}} param.  I don't think I'll 
get around to updating the routing logic to look at a {{\_root_}} field, and 
it's nice knowing we have a work-around By using the {{/32!}} separator.  
Another work-around would be using {{router.field=\_root_}} if you _always_ 
pass in this field.)

Moving "environment" field into comment. This comment was made by dsmiley on 
2021-01-06:

{quote}
Updating to make a blocker for 9.0 because I really want to remove the 9.0 hack 
RE _route_ param. I don't think I'll get around to updating the routing logic 
to look at a _root_ field, and it's nice knowing we have a work-around By using 
the /32! separator. Another work-around would be using router.field=_root_ if 
you always pass in this field.
{quote}

> Atomic/partial updates to nested docs should not assume _route_ param is the 
> root ID
> ------------------------------------------------------------------------------------
>
>                 Key: SOLR-15064
>                 URL: https://issues.apache.org/jira/browse/SOLR-15064
>             Project: Solr
>          Issue Type: Improvement
>            Reporter: David Smiley
>            Assignee: David Smiley
>            Priority: Blocker
>              Labels: NestedDocuments
>             Fix For: 9.0
>
>
> In SOLR-14923, doing an atomic/partial update to a child doc requires 
> indicating what the root doc ID is.  Formerly Solr tried to figure this out 
> automatically, but that had costly implications.   SOLR-14923 adds a 
> temporary hack that assumes that the \_route_ paramter *is* the root ID, if 
> the \_root_ field is not on the doc.  But that's not necessarily accurate, so 
> it should be removed.
>  



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to