[
https://issues.apache.org/jira/browse/AMBARI-21836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16147905#comment-16147905
]
Swapan Shridhar commented on AMBARI-21836:
------------------------------------------
commit
branch-2.6:
{code}
commit b3e8fda82c3f5f95b5b1f7d7c30dc1c61136a7e5
Author: Nishant <[email protected]>
Date: Tue Aug 29 11:48:37 2017 +0530
AMBARI-21836. Fix Upgrade failure because of missing table after
AMBARI-21076 checkin. (Nishant Bangarwa via Swapan Shridhar).
{code}
trunk:
{code}
commit d4ba96481c76487bc1fdd7fbde8392bc97c3226d
Author: Nishant <[email protected]>
Date: Tue Aug 29 11:48:37 2017 +0530
AMBARI-21836. Fix Upgrade failure because of missing table after
AMBARI-21076 checkin.
{code}
CC [~nishantbangarwa]
> 2.6.0 Upgrade Fails Because Of Missing Table
> --------------------------------------------
>
> Key: AMBARI-21836
> URL: https://issues.apache.org/jira/browse/AMBARI-21836
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: trunk, 2.5.1
> Reporter: Nishant Bangarwa
> Assignee: Nishant Bangarwa
> Fix For: trunk, 2.6.0
>
> Attachments: AMBARI-21836.patch
>
>
> STR:
> Install Ambari 2.5
> Upgrade to Ambari 2.6
> The following code is throwing a table not found exception:
> String supersetConfigMappingRemoveSQL = String.format(
> "DELETE FROM %s WHERE type_name like '%s%%'",
> CLUSTER_CONFIG_MAPPING_TABLE, configPrefix);
> This was introduced in AMBARI-21076. The problem is that the
> clusterconfigmapping table no longer exists...
> Options
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)