[ 
https://issues.apache.org/jira/browse/AMBARI-19957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15861361#comment-15861361
 ] 

Hadoop QA commented on AMBARI-19957:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  
http://issues.apache.org/jira/secure/attachment/12852045/AMBARI-19957-DB-checks_trunk_v1.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 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

    {color:red}-1 core tests{color}.  The patch failed these unit tests in 
ambari-server:

                  org.apache.ambari.server.state.cluster.ClusterDeadlockTest

Test results: 
https://builds.apache.org/job/Ambari-trunk-test-patch/10512//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/10512//console

This message is automatically generated.

> Implement new DB checks for Postgres to prevent cross-schema confusion
> ----------------------------------------------------------------------
>
>                 Key: AMBARI-19957
>                 URL: https://issues.apache.org/jira/browse/AMBARI-19957
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.5.0
>            Reporter: Balázs Bence Sári
>            Assignee: Balázs Bence Sári
>             Fix For: 3.0.0, 2.5.0
>
>         Attachments: AMBARI-19957-DB-checks_trunk_v1.patch
>
>
> Postgres allows multiple schemas on a database user's search path, that is 
> users can query from tables in different schemas without the need of 
> prefixing the tables in the query. 
> This can lead to confusion when after an unsuccessful upgrade DBA's restore 
> the tables into a different schema (e.g. public) to Ambari's configured one. 
> As a result, Ambari server may see corrupt data.
> New consistency checks on server startup should warn the user in such 
> situations.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to