You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ambari.apache.org by "Dmytro Sen (JIRA)" <ji...@apache.org> on 2014/10/08 18:01:34 UTC

[jira] [Resolved] (AMBARI-6911) Config_data column should be consistent across tables

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

Dmytro Sen resolved AMBARI-6911.
--------------------------------
    Resolution: Fixed

Committed to trunk and branch-1.7.0

> Config_data column should be consistent across tables
> -----------------------------------------------------
>
>                 Key: AMBARI-6911
>                 URL: https://issues.apache.org/jira/browse/AMBARI-6911
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 1.7.0
>            Reporter: Dmytro Sen
>            Assignee: Dmytro Sen
>             Fix For: 1.7.0
>
>
> config_data column has different types in different tables in MySQL and Postgres.
> MySQL
> clusterconfig - LONGTEXT
> blueprint_configuration - VARCHAR(32000)
> hostgroup_configuration - TEXT
> Postgres & embedded
> clusterconfig - VARCHAR(32000)
> blueprint_configuration - varchar(32000)
> hostgroup_configuration - TEXT
> If we want this fixed, we should take care of upgrading Ambari also.
> MySQL should be mapped to LONGTEXT
> Postrges to TEXT
> Oracle to CLOB



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