Uploaded image for project: 'Kudu'
  1. Kudu
  2. KUDU-1159

Impala sinks should validate column indexes after opening table

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: Private Beta
    • Fix Version/s: n/a
    • Component/s: impala
    • Labels:
      None

      Description

      Through the API, I dropped a column (the last one) from a Kudu table, and then issued an update of the dropped column. Apparently, the sink was still using a column index calculated based on the impala-side table descriptor, rather than looking up the column index from the schema seen when it opened the table. This caused it to call set() with an invalid index and crash impalad.

      This can probably be reproed without an ALTER TABLE by just creating a mapping table that doesn't actually match the underlying schema, and then trying to perform an insert or update.

        Attachments

          Activity

            People

            • Assignee:
              dralves David Alves
              Reporter:
              tlipcon Todd Lipcon
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: