[ 
https://issues.apache.org/jira/browse/HIVE-29659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jide resolved HIVE-29659.
-------------------------
    Fix Version/s: 4.2.0
       Resolution: Duplicate

> DoubleColumnStatsMerger.setHighValue writes to lowValue field instead of 
> highValue
> ----------------------------------------------------------------------------------
>
>                 Key: HIVE-29659
>                 URL: https://issues.apache.org/jira/browse/HIVE-29659
>             Project: Hive
>          Issue Type: Bug
>          Components: Metastore
>            Reporter: Jide
>            Priority: Major
>             Fix For: 4.2.0
>
>
> DoubleColumnStatsMerger.setHighValue() calls 
> aggregateData.setLowValue(highValue) instead of 
> aggregateData.setHighValue(highValue). This causes the merged maximum value 
> to overwrite the minimum field, resulting in min > max after merge. The bug 
> was undetected because the native Hive Metastore writes to a JDO database 
> that does not validate min <= max.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to