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

min(), max() does not handle null properly

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 0.10.0
    • Component/s: None
    • Labels:
      None

      Description

      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.

        Attachments

          Activity

            People

            • Assignee:
              sirpkt Keuntae Park
              Reporter:
              sirpkt Keuntae Park
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: