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

Kudu tables created before IMPALA-3719 cannot load after upgrade

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Critical
    • Resolution: Works for Me
    • Affects Version/s: Kudu_Impala
    • Fix Version/s: Impala 2.8.0
    • Component/s: Frontend
    • Labels:

      Description

      Tables created before IMPALA-3719 (Simplify CREATE TABLE Kudu statements) added a table property for the PK columns. That property is no longer used and an analysis exception is thrown if it is found to indicate that the user should only use the new syntax. We should still throw if the PK syntax isn't provided, but we shouldn't throw if the tbl property is also provided.

        Activity

        Hide
        twmarshall Thomas Tauber-Marshall added a comment -

        I manually created a variety of Kudu tables (internal/external, hash/range, different replication factors, etc.) with the old code on a CM cluster, then upgraded the cluster and all the tables loaded fine and were accessible, including creating an external table backed by a table created with the old code, so there doesn't appear to be any issue here.

        Show
        twmarshall Thomas Tauber-Marshall added a comment - I manually created a variety of Kudu tables (internal/external, hash/range, different replication factors, etc.) with the old code on a CM cluster, then upgraded the cluster and all the tables loaded fine and were accessible, including creating an external table backed by a table created with the old code, so there doesn't appear to be any issue here.

          People

          • Assignee:
            twmarshall Thomas Tauber-Marshall
            Reporter:
            mjacobs Matthew Jacobs
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development