[jira] [Commented] (AMBARI-10022) RU - DB Schema differs between Postgres internal and external

["Hadoop QA (JIRA)" <ji...@apache.org>]

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

Hadoop QA commented on AMBARI-10022:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12703806/AMBARI-10022.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:red}-1 tests included{color}.  The patch doesn't appear to include any new or modified tests.
                        Please justify why no new tests are needed for this patch.
                        Also please list what manual steps were performed to verify this patch.

    {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 test build failed in ambari-server 

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

This message is automatically generated.

> RU - DB Schema differs between Postgres internal and external
> -------------------------------------------------------------
>
>                 Key: AMBARI-10022
>                 URL: https://issues.apache.org/jira/browse/AMBARI-10022
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.0.0
>            Reporter: Alejandro Fernandez
>            Assignee: Alejandro Fernandez
>             Fix For: 2.0.0
>
>         Attachments: AMBARI-10022.patch
>
>
> The DB schema differs between the internal and external Postgres databases, and this affects RU.
> Impact: If not fixed in Ambari 2.0, then a future release will have to absorb the technical debt and need the Ambari Update to correct the schema in order to keep it consistent in order to prevent bugs.
>  
> Ambari-DDL-Postgres-EMBEDDED-CREATE.sql
> {code}
> CREATE TABLE ambari.repo_version (
>   repo_version_id BIGINT,  -- should have NOT NULL modifier
>   ...
>   INSERT INTO ambari_sequences (sequence_name, sequence_value)
>   ...
>   union all
>   select 'upgrade_group_id_seq', 0 
> {code}
> vs
> Ambari-DDL-Postgres-CREATE.sql
> {code}
> CREATE TABLE ambari.repo_version (
>   repo_version_id BIGINT NOT NULL,
>   ...
> INSERT INTO ambari_sequences (sequence_name, sequence_value)
> ...
> -- Doesn't insert upgrade_group_id_seq
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)