You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@calcite.apache.org by "dijkspicy (JIRA)" <ji...@apache.org> on 2019/04/30 02:14:00 UTC
[jira] [Created] (CALCITE-3039) Why MinFloat use Math::min while
MinDouble use Math::max as its comparision in AggragateNode ?
dijkspicy created CALCITE-3039:
----------------------------------
Summary: Why MinFloat use Math::min while MinDouble use Math::max as its comparision in AggragateNode ?
Key: CALCITE-3039
URL: https://issues.apache.org/jira/browse/CALCITE-3039
Project: Calcite
Issue Type: Bug
Components: core
Affects Versions: 1.17.0
Reporter: dijkspicy
/** Implementation of {@code MIN} function to calculate the minimum of
* {@code float} values as a user-defined aggregate.
*/
public static class MinFloat extends NumericComparison<Float> {
public MinFloat() {
super(Float.MAX_VALUE, Math::min);
}
}
/** Implementation of {@code MIN} function to calculate the minimum of
* {@code double} and {@code real} values as a user-defined aggregate.
*/
public static class MinDouble extends NumericComparison<Double> {
public MinDouble() {
super(Double.MAX_VALUE, Math::max);
}
}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)