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] [Updated] (TAJO-182) Comparison of primitive values including null value should return NULL.
Date Sun, 22 Dec 2013 14:51:51 GMT

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

Hyunsik Choi updated TAJO-182:
------------------------------

    Description: 
-If some domain value is compared to Null value, the current implementation will cause InvalidOperationException.
Such cases should result in 'false'.-

-If some domain value is compared to Null value, the current implementation will cause either
InvalidOperationException or FALSE. Such cases should result in NULL.-

Many primitive operators including arithmetic and comparison do not consider three valued
logic. This patch corrects this problem. The original issue title was 'Comparison of primitive
values including null value should return NULL.' This issue was expanded for null value handling
of all primitive operators.

  was:
-If some domain value is compared to Null value, the current implementation will cause InvalidOperationException.
Such cases should result in 'false'.-

If some domain value is compared to Null value, the current implementation will cause either
InvalidOperationException or FALSE. Such cases should result in NULL.


> Comparison of primitive values including null value should return NULL.
> -----------------------------------------------------------------------
>
>                 Key: TAJO-182
>                 URL: https://issues.apache.org/jira/browse/TAJO-182
>             Project: Tajo
>          Issue Type: Bug
>          Components: planner/optimizer
>            Reporter: Hyunsik Choi
>            Assignee: Hyunsik Choi
>            Priority: Critical
>             Fix For: 0.8-incubating
>
>         Attachments: TAJO-182.patch, TAJO-182_2.patch
>
>
> -If some domain value is compared to Null value, the current implementation will cause
InvalidOperationException. Such cases should result in 'false'.-
> -If some domain value is compared to Null value, the current implementation will cause
either InvalidOperationException or FALSE. Such cases should result in NULL.-
> Many primitive operators including arithmetic and comparison do not consider three valued
logic. This patch corrects this problem. The original issue title was 'Comparison of primitive
values including null value should return NULL.' This issue was expanded for null value handling
of all primitive operators.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message