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

schematool version info exit status should depend on compatibility, not equality

Log workAgile BoardRank to TopRank to BottomBulk Copy AttachmentsBulk Move AttachmentsVotersWatch issueWatchersCreate sub-taskConvert to sub-taskMoveLinkCloneLabelsUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    Description

      Newer versions of metastore schema are compatible with older versions of hive, as only new tables or columns are added with additional information.

      HIVE-11613 added a check in hive schematool -info command to see if schema version is equal.

      However, the state where db schema version is ahead of hive software version is often seen when a 'rolling upgrade' or 'rolling downgrade' is happening. This is a state where hive is functional and returning non zero status for it is misleading.

      Attachments

        1. HIVE-12261.1.patch
          7 kB
          Thejas Nair
        2. HIVE-12261-branch-1.0.0.patch
          8 kB
          Thejas Nair
        3. HIVE-12261-branch-1.patch
          6 kB
          Thejas Nair

        Issue Links

        Activity

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

          People

            thejas Thejas Nair Assign to me
            thejas Thejas Nair
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Time Tracking

              Estimated:
              Original Estimate - Not Specified
              Not Specified
              Remaining:
              Remaining Estimate - 0h
              0h
              Logged:
              Time Spent - 20m
              20m

              Slack

                Issue deployment