[
https://issues.apache.org/jira/browse/HIVE-12261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14973109#comment-14973109
]
ASF GitHub Bot commented on HIVE-12261:
---------------------------------------
GitHub user thejasmn opened a pull request:
https://github.com/apache/hive/pull/51
HIVE-12261
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/thejasmn/hive HIVE-12261
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/hive/pull/51.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #51
----
commit 9728b203cce09d56ce2417c5023f56e8ef061dea
Author: thejas nair <[email protected]>
Date: 2015-10-25T07:04:12Z
Merge pull request #3 from apache/master
x
commit 31adb2b220967667cd06ea77dcd53b37003552fb
Author: Thejas Nair <[email protected]>
Date: 2015-10-25T06:56:38Z
HIVE-12261
----
> 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)
