[
https://issues.apache.org/jira/browse/TAJO-1265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14255536#comment-14255536
]
ASF GitHub Bot commented on TAJO-1265:
--------------------------------------
Github user sirpkt commented on the pull request:
https://github.com/apache/tajo/pull/315#issuecomment-67810799
@hyunsik Sorry for the incomplete patch.
There are many test cases related with max(), min() and I missed the
testing for all those cases.
I apologize for stealing your time by faulty patch.
I'll check and update the patch.
> 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)
