[
https://issues.apache.org/jira/browse/AMBARI-10022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14358046#comment-14358046
]
Hudson commented on AMBARI-10022:
---------------------------------
FAILURE: Integrated in Ambari-trunk-Commit #2012 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/2012/])
AMBARI-10022. RU - DB Schema differs between Postgres internal and external
(alejandro) (afernandez:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=4d1334719e92c2dfa5327675995ce44593772177)
* ambari-server/src/main/resources/Ambari-DDL-Postgres-CREATE.sql
* ambari-server/src/main/resources/Ambari-DDL-Postgres-EMBEDDED-CREATE.sql
> 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)
