[
https://issues.apache.org/jira/browse/AMBARI-19957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15868174#comment-15868174
]
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/12852834/AMBARI-19957-DB-checks_25_v4.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10592//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_25_v4.patch,
> AMBARI-19957-DB-checks_trunk_v4.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)
