[CRUNCH-503] Behavior of MAX_N Aggregator for duplicate values is counter-intuitive

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.11.0
• Fix Version/s: 0.12.0
• Component/s: Core
• Assignee: Josh Wills
• Reporter: Tycho Lamerigts
• Created: 19/Mar/15 10:39
• Updated: 18/May/15 19:04
• Resolved: 19/Mar/15 22:58

Description

I would expect code below to return {1, 2, 3}. Instead, it returns {2, 3}.

public class MaxNAggregatorTest {

    @Test
    public void duplicateMaxNValueShouldBeIgnored() {
        Aggregator<Integer> myAggregator = Aggregators.MAX_N(3, Integer.class);
        myAggregator.reset();
        myAggregator.update(1);
        myAggregator.update(2);
        myAggregator.update(3);
        myAggregator.update(3);
        assertEquals(3, Iterables.size(myAggregator.results()));
    }
}