You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tajo.apache.org by "Keuntae Park (JIRA)" <ji...@apache.org> on 2014/12/22 06:15:13 UTC
[jira] [Created] (TAJO-1265) min(), max() does not handle null
properly
Keuntae Park created TAJO-1265:
----------------------------------
Summary: min(), max() does not handle null properly
Key: TAJO-1265
URL: https://issues.apache.org/jira/browse/TAJO-1265
Project: Tajo
Issue Type: Bug
Reporter: Keuntae Park
Assignee: Keuntae Park
Priority: Minor
In other DBs like oracle and postgreSQL,
null is excluded from calculation of min() and max() value until there is no non-null value in the given column, in which case, it returns null.
However, current implementation of Tajo considers null as
0 for int or long column, 0.0 for float or double column, or "" for text column.
It needs to handle null value separately from non-null values in min() and max() calculation.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)