You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Balázs Bence Sári (JIRA)" <ji...@apache.org> on 2017/03/16 09:37:41 UTC

[jira] [Updated] (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:all-tabpanel ]

Balázs Bence Sári updated AMBARI-19957:
---------------------------------------
    Resolution: Fixed
        Status: Resolved  (was: Patch Available)

> 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)