[HBASE-5821] Incorrect handling of null value in Coprocessor aggregation function min()

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.92.1
• Fix Version/s: 0.92.2
• Component/s: Coprocessors
• Hadoop Flags: Reviewed
• Assignee: Wei Xue
• Reporter: Wei Xue
• Created: 18/Apr/12 14:21
• Updated: 20/Nov/15 11:53
• Resolved: 30/Jul/12 15:32

Description

Both in AggregateImplementation and AggregationClient, the evaluation of the current minimum value is like:
min = (min == null || ci.compare(result, min) < 0) ? result : min;

The LongColumnInterpreter takes null value is treated as the least value, while the above expression takes min as the greater value when it is null. Thus, the real minimum value gets discarded if a null value comes later.
max() could also be wrong if a different ColumnInterpreter other than LongColumnInterpreter treats null value differently (as the greatest).