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

samuel ma updated SOLR-15540:
-----------------------------
    Summary: Duplicated adding document for update when Solr7 upgrade to Solr8  
(was: Duplicated adding document  when Solr7 upgrade to Solr8)

> Duplicated adding document for update when Solr7 upgrade to Solr8
> -----------------------------------------------------------------
>
>                 Key: SOLR-15540
>                 URL: https://issues.apache.org/jira/browse/SOLR-15540
>             Project: Solr
>          Issue Type: Bug
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: update, UpdateRequestProcessors
>    Affects Versions: 8.8.2
>         Environment: SolrCloud Solr 8.8.2
>            Reporter: samuel ma
>            Priority: Major
>
> We upgrade Solr7.7.2 to Solr8.8.2, keep using the Solr 7 index data, the 
> query operation is fine. But when we try to add the doc (with the same doc 
> id, actually is an update operation) to Solr8, we actually see 2 doc with the 
> same id, which means the update did not remove the Solr7 doc.
>  
>  
> Below is the schema.xml configuration:
>  
> {code:java}
> <field name="id" type="string" indexed="true" stored="true" required="true" 
> multiValued="false" />
> <field name="_root_" type="string" indexed="true" stored="false"/>
> <uniqueKey>id</uniqueKey>
> {code}
>  
> Also add nested field in Solr8
> {code:java}
> <fieldType name="_nest_path_" class="solr.NestPathField" />{code}
>  
> I can see in Sol7 code
> {code:java}
> DirectUpdateHandler2.updateDocOrDocValues{code}
> use the idTerm as updateTerm, but in this case Solr8 use rootTerm as the 
> updateTerm. is this an expected behavior?
>  
>  



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

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

Reply via email to