[
https://issues.apache.org/jira/browse/AMBARI-21836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16144909#comment-16144909
]
Hadoop QA commented on AMBARI-21836:
------------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12884193/AMBARI-21836.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12079//console
This message is automatically generated.
> 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
> 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)
