You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Jonathan Hurley (JIRA)" <ji...@apache.org> on 2015/04/16 16:38:59 UTC

[jira] [Resolved] (AMBARI-10511) Use Stack Table For Entity Relationships

     [ https://issues.apache.org/jira/browse/AMBARI-10511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonathan Hurley resolved AMBARI-10511.
--------------------------------------
    Resolution: Fixed

> Use Stack Table For Entity Relationships
> ----------------------------------------
>
>                 Key: AMBARI-10511
>                 URL: https://issues.apache.org/jira/browse/AMBARI-10511
>             Project: Ambari
>          Issue Type: Task
>          Components: ambari-server
>    Affects Versions: 2.1.0
>            Reporter: Jonathan Hurley
>            Assignee: Jonathan Hurley
>            Priority: Critical
>             Fix For: 2.1.0
>
>
> The following tables reference the desired/current stack using a JSON string.  These will need to be replaced by using the {{stack.stack_id}} reference column:
> - clusters.desired_stack_version
> - clusterstate.current_stack_version
> - hostcomponentdesiredstate.desired_stack_version
> - hostcomponentstate.current_stack_version
> - servicecomponentdesiredstate.desired_stack_version
> - blueprint.stack_name, blueprint.stack_version
> - repo_version.stack
> Add FK to stack.stack_id for tables and columns above. {{UpgradeCatalog210}} also needs to calculate the correct stack that the Ambari 2.0.0 cluster is using in addition to making the appropriate column changes.
> In addition to the above changes, new fields will need to be added to the following tables in order to associate the service configuration version and the individual configuration types with the stack that they belong to.
> - serviceconfig
> - clusterconfig
> Although there may be service configurations saved from a prior manual stack upgrade, these will all be marked with the current HDP stack version as there will be no way to determine which prior version was associated with a particular stack. 



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