Uploaded image for project: 'Tajo'
  1. Tajo
  2. TAJO-182

Correct NULL value handling of primitive operators

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 0.8.0
    • Component/s: Planner/Optimizer
    • Labels:
      None

      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.

        Attachments

        1. TAJO-182.patch
          29 kB
          Hyunsik Choi
        2. TAJO-182_3.patch
          78 kB
          Hyunsik Choi
        3. TAJO-182_2.patch
          76 kB
          Hyunsik Choi

          Issue Links

            Activity

              People

              • Assignee:
                hyunsik Hyunsik Choi
                Reporter:
                hyunsik Hyunsik Choi
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: