[jira] [Commented] (AMBARI-19957) Implement new DB checks for Postgres to prevent cross-schema confusion
[
https://issues.apache.org/jira/browse/AMBARI-19957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15869975#comment-15869975
]
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/12853047/AMBARI-19957-DB-checks_25_v4_rebase1.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/10616//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_rebase1.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)
[jira] [Commented] (AMBARI-19957) Implement new DB checks for Postgres to prevent cross-schema confusion
[ https://issues.apache.org/jira/browse/AMBARI-19957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15869951#comment-15869951 ] Hudson commented on AMBARI-19957: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #1014 (See [https://builds.apache.org/job/Ambari-branch-2.5/1014/]) AMBARI-19957. Implement new DB checks for Postgres to prevent (stoader: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=04ec37d24800a78d628920c8a53306f1bc54d5c0]) * (edit) ambari-server/src/main/java/org/apache/ambari/server/checks/DatabaseConsistencyCheckHelper.java * (add) ambari-server/src/main/java/org/apache/ambari/server/checks/DatabaseConsistencyCheckResult.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariServer.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/checks/DatabaseConsistencyCheckHelperTest.java * (edit) ambari-server/src/main/python/ambari_server_main.py * (edit) ambari-server/src/main/java/org/apache/ambari/server/checks/DatabaseConsistencyChecker.java > 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_rebase1.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)
[jira] [Commented] (AMBARI-19957) Implement new DB checks for Postgres to prevent cross-schema confusion
[ https://issues.apache.org/jira/browse/AMBARI-19957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15869858#comment-15869858 ] Hudson commented on AMBARI-19957: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6760 (See [https://builds.apache.org/job/Ambari-trunk-Commit/6760/]) AMBARI-19957. Implement new DB checks for Postgres to prevent (stoader: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=fa527360b28e956e3e931449e8740ed07ed407ed]) * (edit) ambari-server/src/main/python/ambari_server_main.py * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariServer.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/checks/DatabaseConsistencyCheckHelperTest.java * (add) ambari-server/src/main/java/org/apache/ambari/server/checks/DatabaseConsistencyCheckResult.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/checks/DatabaseConsistencyChecker.java * (edit) ambari-server/src/main/java/org/apache/ambari/server/checks/DatabaseConsistencyCheckHelper.java > 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)
[jira] [Commented] (AMBARI-19957) Implement new DB checks for Postgres to prevent cross-schema confusion
[
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)
[jira] [Commented] (AMBARI-19957) Implement new DB checks for Postgres to prevent cross-schema confusion
[
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)
