[jira] [Updated] (HIVE-12261) schematool version info exit status should depend on compatibility, not equality

["ASF GitHub Bot (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HIVE-12261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

ASF GitHub Bot updated HIVE-12261:
----------------------------------
    Labels: pull-request-available  (was: )

> schematool version info exit status should depend on compatibility, not equality
> --------------------------------------------------------------------------------
>
>                 Key: HIVE-12261
>                 URL: https://issues.apache.org/jira/browse/HIVE-12261
>             Project: Hive
>          Issue Type: Bug
>          Components: Metastore
>    Affects Versions: 1.3.0, 2.0.0
>            Reporter: Thejas Nair
>            Assignee: Thejas Nair
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.3.0, 2.0.0
>
>         Attachments: HIVE-12261-branch-1.0.0.patch, HIVE-12261-branch-1.patch, HIVE-12261.1.patch
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)