lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tim Owen (JIRA)" <>
Subject [jira] [Created] (SOLR-9505) Extra tests to confirm Atomic Update remove behaviour
Date Tue, 13 Sep 2016 09:38:20 GMT
Tim Owen created SOLR-9505:

             Summary: Extra tests to confirm Atomic Update remove behaviour
                 Key: SOLR-9505
             Project: Solr
          Issue Type: Test
      Security Level: Public (Default Security Level. Issues are Public)
    Affects Versions: master (7.0)
            Reporter: Tim Owen
            Priority: Minor

The behaviour of the Atomic Update {{remove}} operation in the code doesn't match the description
in the Confluence documentation, which has been questioned already. From looking at the source
code, and using curl to confirm, the {{remove}} operation only removes the first occurrence
of a value from a multi-valued field, it does not remove all occurrences. The {{removeregex}}
operation does remove all, however.

There are unit tests for Atomic Updates, but they didn't assert this behaviour, so I've added
some extra assertions to confirm that, and a couple of extra tests including one that checks
that {{removeregex}} does a Regex match of the whole value, not just a find-anywhere operation.

I think it's the documentation that needs clarifying - the code behaves as expected (assuming
{{remove}} was intended to work that way?)

This message was sent by Atlassian JIRA

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

View raw message