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

Ishan Chattopadhyaya edited comment on SOLR-8276 at 11/11/15 4:14 AM:
----------------------------------------------------------------------

Adding a patch that populates the non-stored, non-multivalued docvalues fields 
during the atomic updates.

I couldn't test for multivalued non-stored docvalues fields, since I got the 
following exception during the field() function query on a multivalued field: 
{{can not use FieldCache on multivalued field: intdvMulti}}. Am I missing 
something obvious?

I think doing this for non-multivalued fields itself is an improvement, and 
that the case of multivalued fields can be dealt with separately.


was (Author: ichattopadhyaya):
Adding a patch that populates the non-stored, non-multivalued docvalues fields 
during the atomic updates.

I couldn't test for multivalued non-stored docvalues fields, since I got the 
following exception during the field() function query on a multivalued field:
{{can not use FieldCache on multivalued field: intdvMulti}}
Am I missing something obvious?

I think doing this for non-multivalued fields itself is an improvement, and 
that the case of multivalued fields can be dealt separately.

> Atomic updates with non-stored docvalues don't work
> ---------------------------------------------------
>
>                 Key: SOLR-8276
>                 URL: https://issues.apache.org/jira/browse/SOLR-8276
>             Project: Solr
>          Issue Type: Bug
>            Reporter: Ishan Chattopadhyaya
>         Attachments: SOLR-8276.patch
>
>
> Currently, for atomic updates, the non-stored docvalues fields are neither 
> carried forward to updated document, not do operations like "inc" work on 
> them.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

Reply via email to