[TAJO-182] Correct NULL value handling of primitive operators

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Fix Version/s: 0.8.0
• Component/s: Planner/Optimizer
• Assignee: Hyunsik Choi
• Reporter: Hyunsik Choi
• Created: 15/Sep/13 10:13
• Updated: 23/Dec/13 07:33
• Resolved: 23/Dec/13 05:18

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.

Issue Links

• is related to: TAJO-450 Incorrect inet4datum comparison