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

Jason Gerlowski commented on SOLR-13539:
----------------------------------------

Hi [~TimOwen] and [~thomas.woeckinger], wanted to follow up on this.

As far as I know, all the pieces of this are now merged into {{master}}.

# the original fixes for the UUID, bool, enum, etc. field types
# Introduce an EmbeddedSolrServer test base-class (PR: 755)
# New Xml and Javabin tests (PR: 665)
# The patch attached on this issue covering a gap around mv removeregex 
operations
# Some additional test cases and changes Tim authored on SOLR-9505.

Have I missed anything in the list above?  I'm working on backporting these 
changes now so that they can all go into the 8.3 release.  Once that 
backporting is done I'll close this and the related issues.  But if I've missed 
anything, let me know!

> Atomic Update Multivalue remove does not work for field types UUID, Enums, 
> Bool  and Binary
> -------------------------------------------------------------------------------------------
>
>                 Key: SOLR-13539
>                 URL: https://issues.apache.org/jira/browse/SOLR-13539
>             Project: Solr
>          Issue Type: Bug
>          Components: UpdateRequestProcessors
>    Affects Versions: 7.7.2, 8.1, 8.1.1
>            Reporter: Thomas Wöckinger
>            Assignee: Jason Gerlowski
>            Priority: Critical
>         Attachments: SOLR-13539.patch
>
>          Time Spent: 12h
>  Remaining Estimate: 0h
>
> When using JavaBinCodec the values of collections are of type 
> ByteArrayUtf8CharSequence, existing field values are Strings so the remove 
> Operation does not have any effect.
>  This is related to following field types: UUID, Enums, Bool and Binary



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

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

Reply via email to