Uploaded image for project: 'IMPALA'
  1. IMPALA
  2. IMPALA-2740

kudu-table-scanner does not reset null-bits for non-matching rows

    Details

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

      Description

      When a column value is set to NULL and the row is filtered out in the predicate evaluation in the KuduTableScanner, the null-bits are not cleared. If now, the next row matches and the values are copied, the null-bits are still showing the column set to NULL even though a value exists. This will produce incorrect results.

      Only after a row matched, the null-bits are rest for the new row (cf. https://github.com/cloudera/impala-kudu/blob/feature/kudu/be/src/exec/kudu-scanner.cc#L205)

        Attachments

          Activity

            People

            • Assignee:
              caseyc casey
              Reporter:
              mgrund_impala_bb91 Martin Grund
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: