Mailing-List: contact dev-help@hive.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hive.apache.org
Date: Mon, 12 May 2014 22:06:16 +0000 (UTC)
From: "Carl Steinbach (JIRA)" <jira@apache.org>
To: hive-dev@hadoop.apache.org
Message-ID: <JIRA.12710444.1398378820317.333107.1399932376596@arcas>
In-Reply-To: <JIRA.12710444.1398378820317@arcas>
References: <JIRA.12710444.1398378820317@arcas>
Subject: [jira] [Resolved] (HIVE-6974) Make Metastore Version Check work
 with Custom version suffixes
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Carl Steinbach resolved HIVE-6974.
----------------------------------

    Resolution: Duplicate

> Make Metastore Version Check work with Custom version suffixes
> --------------------------------------------------------------
>
>                 Key: HIVE-6974
>                 URL: https://issues.apache.org/jira/browse/HIVE-6974
>             Project: Hive
>          Issue Type: Bug
>          Components: Metastore
>            Reporter: Carl Steinbach
>
> HIVE-3764 added support for doing a version consistency check between the Hive JARs on the classpath and the metastore schema in the backend database. This is a nice feature, but it currently doesn't work for well for folks who appending the release version with their own suffixes, e.g. "0.12.0.li_20".
> We can fix this problem by modifying MetaStoreSchemaInfo.getHiveSchemaVersion() to match against ^\d+\.\d+\.\d+ and ignore anything that remains.


--
This message was sent by Atlassian JIRA
(v6.2#6252)