lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Noble Paul (JIRA)" <>
Subject [jira] [Commented] (SOLR-13331) Atomic Update Multivalue remove does not work
Date Wed, 15 May 2019 21:22:00 GMT


Noble Paul commented on SOLR-13331:

bq. I couldn't of said it better myself. Very concerning. 

After the bugs surfaced I realized one thing , almost none of our tests use javabin which
is the most commonly used format . if we had any of these tests using javabin, it could've
been caught and rectified. 

We need to ensure that tests run with javabin too.

> Atomic Update Multivalue remove does not work
> ---------------------------------------------
>                 Key: SOLR-13331
>                 URL:
>             Project: Solr
>          Issue Type: Bug
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: UpdateRequestProcessors
>    Affects Versions: 7.7, 7.7.1, 8.0
>         Environment: Standalone Solr Server
>            Reporter: Thomas Wöckinger
>            Assignee: Jason Gerlowski
>            Priority: Critical
>              Labels: patch, pull-request-available, ready-to-commit, test
>             Fix For: 7.7.2, 8.1, master (9.0)
>         Attachments: Fix-SOLR13331-Add-toNativeType-implementations.patch, SOLR-13331.patch
>          Time Spent: 20m
>  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.
> The relevant code is located in class AtomicUpdateDocumentMerger method doRemove.
> The method parameter fieldVal contains the collection values of type ByteArrayUtf8CharSequence,
the variable original contains the collection of Strings

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message