You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Srimanth Gunturi (JIRA)" <ji...@apache.org> on 2016/04/25 20:32:13 UTC
[jira] [Updated] (AMBARI-15098) Ambari Schema Version should ignore
patch number from version number
[ https://issues.apache.org/jira/browse/AMBARI-15098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Srimanth Gunturi updated AMBARI-15098:
--------------------------------------
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Ambari Schema Version should ignore patch number from version number
> --------------------------------------------------------------------
>
> Key: AMBARI-15098
> URL: https://issues.apache.org/jira/browse/AMBARI-15098
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.2.1
> Reporter: Jayush Luniya
> Assignee: Jayush Luniya
> Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15098.patch
>
>
> # On ambari-server upgrade to a patch release version (2.0.2 -> 2.2.1.2), ambari server fails to start.
> # This is because the schema version set in the DB on ambari-server upgrade is 2.2.1 whereas ambari-server version is 2.2.1.2.
> # This incosistency leads to DB check failure. DB check should ignore patch release number from the ambari version.
> # Further a clean install on 2.2.1.2 will set the DB schema version to 2.2.1.2 whereas an upgrade to 2.2.1.2 will set the DB schema version to 2.2.1
> # We should fix this inconsistency by always setting DB schema version to 3-digit and ignoring the patch release version during DB check.
> # We will not be supporting DB schema changes in patch releases.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)