tajo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hyunsik Choi (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (TAJO-182) Null comparison should be false
Date Wed, 18 Dec 2013 06:39:11 GMT

    [ https://issues.apache.org/jira/browse/TAJO-182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13851431#comment-13851431
] 

Hyunsik Choi commented on TAJO-182:
-----------------------------------

Hi Prafulla,

Thank you for reminding this issue!! Yes, you are right. Exactly, null comparison should result
in NULL value instead of false value. Actually, almost of all functions are doing that. But,
operators between primitive values does not so. This issue was intended to an temporal solution.
We have to fix this issue.

> Null comparison should be false
> -------------------------------
>
>                 Key: TAJO-182
>                 URL: https://issues.apache.org/jira/browse/TAJO-182
>             Project: Tajo
>          Issue Type: Bug
>          Components: planner/optimizer
>            Reporter: Hyunsik Choi
>             Fix For: 0.8-incubating
>
>
> If some domain value is compared to Null value, the current implementation will cause
InvalidOperationException. Such cases should result in 'false'.



--
This message was sent by Atlassian JIRA
(v6.1.4#6159)

Mime
View raw message