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

Ishan Chattopadhyaya commented on SOLR-11286:
---------------------------------------------

My guess is this is happening due to AtomicUpdateDocumentMerger's 
computeInPlaceUpdateableFields(), third pass.
{{third pass: requiring checks against the actual IndexWriter due to internal 
DV update limitations}}. If the updateable field doesn't exist in the index 
already, the first update is not an in-place update. If that's the case, the 
feature is working as designed.

> First doc Inplace Update, updating whole document.
> --------------------------------------------------
>
>                 Key: SOLR-11286
>                 URL: https://issues.apache.org/jira/browse/SOLR-11286
>             Project: Solr
>          Issue Type: Bug
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: update
>    Affects Versions: 6.6
>         Environment: <field name="_version_" type="tlong" indexed="false" 
> stored="false" docValues="true"/>
> trying inplace update for 
> <field name="GEN"                     type="tdouble"  indexed="false" 
> stored="false" docValues="true"/>
>            Reporter: Abhishek Umarjikar
>
> I am trying in place update , for first doc the whole document is getting 
> indexed. so in place update is not working for first time. After that it 
> works for remaining docs. I am using solrj for inplace update.
> First Doc For in place update
> *2017-08-24 21:59:14,603 DEBUG org.apache.solr.update.DirectUpdateHandler2  ? 
> updateDocument(add{_version_=1576617435037958144,id=US9668251B2})*
> After First In place update
> *2017-08-24 22:01:33,109 DEBUG org.apache.solr.update.DirectUpdateHandler2  ? 
> updateDocValues(add{_version_=1576617580281462784,id=US2014029560A1})*



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

Reply via email to