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

Support metastore version consistency check

Log workAgile BoardRank to TopRank to BottomVotersWatch issueWatchersCreate sub-taskConvert to sub-taskMoveLinkCloneLabelsUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 0.8.0, 0.9.0, 0.10.0, 0.11.0
    • 0.12.0
    • Metastore
    • None

    Description

      Today there's no version/compatibility information stored in hive metastore. Also the datanucleus configuration property to automatically create missing tables is enabled by default. If you happen to start an older or newer hive or don't run the correct upgrade scripts during migration, the metastore would end up corrupted. The autoCreate schema is not always sufficient to upgrade metastore when migrating to newer release. It's not supported with all databases. Besides the migration often involves altering existing table, changing or moving data etc.

      Hence it's very useful to have some consistency check to make sure that hive is using correct metastore and for production systems the schema is not automatically by running hive.

      Attachments

        1. HIVE-3764.1.patch
          39 kB
          Prasad Suresh Mujumdar
        2. HIVE-3764.2.patch
          40 kB
          Prasad Suresh Mujumdar
        3. HIVE-3764-12.3.patch
          40 kB
          Prasad Suresh Mujumdar
        4. HIVE-3764-trunk.3.patch
          163 kB
          Prasad Suresh Mujumdar

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            prasadm Prasad Suresh Mujumdar Assign to me
            prasadm Prasad Suresh Mujumdar
            Votes:
            0 Vote for this issue
            Watchers:
            9 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Issue deployment