Uploaded image for project: 'Hive'
  1. Hive
  2. HIVE-18220

Workload Management tables have broken constraints defined on postgres schema

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Blocker
    • Resolution: Fixed
    • None
    • 3.0.0
    • Metastore
    • None

    Description

      Schema initialization on Postgres fails with the following error:

      0: jdbc:postgresql://localhost.localdomain:54> ALTER TABLE ONLY "WM_POOL" ADD CO 
      NSTRAINT "UNIQUE_WM_RESOURCEPLAN" UNIQUE ("NAME")
      Error: ERROR: column "NAME" named in key does not exist (state=42703,code=0)
      Closing: 0: jdbc:postgresql://localhost.localdomain:5432/hive
      org.apache.hadoop.hive.metastore.HiveMetaException: Schema initialization FAILED! Metastore state would be inconsistent !!
      Underlying cause: java.io.IOException : Schema script failed, errorcode 2
      org.apache.hadoop.hive.metastore.HiveMetaException: Schema initialization FAILED! Metastore state would be inconsistent !!
        at org.apache.hive.beeline.HiveSchemaTool.doInit(HiveSchemaTool.java:586)
        at org.apache.hive.beeline.HiveSchemaTool.doInit(HiveSchemaTool.java:559)
        at org.apache.hive.beeline.HiveSchemaTool.main(HiveSchemaTool.java:1183)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:498)
        at org.apache.hadoop.util.RunJar.run(RunJar.java:239)
        at org.apache.hadoop.util.RunJar.main(RunJar.java:153)
      Caused by: java.io.IOException: Schema script failed, errorcode 2
        at org.apache.hive.beeline.HiveSchemaTool.runBeeLine(HiveSchemaTool.java:957)
        at org.apache.hive.beeline.HiveSchemaTool.runBeeLine(HiveSchemaTool.java:935)
        at org.apache.hive.beeline.HiveSchemaTool.doInit(HiveSchemaTool.java:582)
        ... 8 more
      

      It is due to couple on incorrect constraint definitions in the schema.

      Attachments

        1. HIVE-18220.patch
          2 kB
          Deepesh Khandelwal

        Activity

          People

            deepesh Deepesh Khandelwal
            deepesh Deepesh Khandelwal
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: