[
https://issues.apache.org/jira/browse/AMBARI-10301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14392107#comment-14392107
]
Hudson commented on AMBARI-10301:
---------------------------------
FAILURE: Integrated in Ambari-trunk-Commit #2174 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/2174/])
AMBARI-10301 - Stack Database Table Creation and Population From Resources
(part3) (jonathanhurley) (jhurley:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=3f452debd86a53dc4ea197dc9944334b03d2c7a9)
* ambari-server/src/main/resources/Ambari-DDL-Postgres-EMBEDDED-CREATE.sql
* ambari-server/src/main/resources/Ambari-DDL-SQLServer-CREATE.sql
* ambari-server/src/main/resources/Ambari-DDL-Postgres-CREATE.sql
> Stack Database Table Creation and Population From Resources
> -----------------------------------------------------------
>
> Key: AMBARI-10301
> URL: https://issues.apache.org/jira/browse/AMBARI-10301
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
> Affects Versions: 2.1.0
> Reporter: Jonathan Hurley
> Assignee: Jonathan Hurley
> Fix For: 2.1.0
>
>
> A new table should be created that contains the stack information for every
> stack defined on the file system of Ambari Server.
> ||column||type||description||
> |stack_id|int|PK|
> |stack_name|varchar|stack name, e.g. 'HDP'|
> |stack_version|varchar|stack version, e.g. '2.2'|
> When Ambari starts up, the server should resolve available stacks and their
> versions on the filesystem with the records available in the new stack table.
> This concept is similar in design to how Alert Definitions are resolved on
> startup.
> This Jira will only cover the table creation and population and will not
> cover any of the foreign key changes required in other tables. Those will be
> in a separate Jira.
> The {{UpgradeCatalog210}} script should also be written to cover the table
> creation.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
