hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thejas M Nair (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HIVE-12261) schematool version info exit status should depend on compatibility, not equality
Date Sun, 25 Oct 2015 06:53:27 GMT

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

Thejas M Nair updated HIVE-12261:
---------------------------------
    Attachment: HIVE-12261-branch-1.patch
                HIVE-12261-branch-1.0.0.patch

> 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 M Nair
>            Assignee: Thejas M Nair
>         Attachments: HIVE-12261-branch-1.0.0.patch, HIVE-12261-branch-1.patch
>
>
> 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
(v6.3.4#6332)

Mime
View raw message