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

Posted to issues@ambari.apache.org by "Myroslav Papirkovskyi (JIRA)" <ji...@apache.org> on 2016/11/28 16:24:58 UTC

[jira] [Updated] (AMBARI-18951) Force InnoDB usage for MySQL

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

Myroslav Papirkovskyi updated AMBARI-18951:
-------------------------------------------
    Summary: Force InnoDB usage for MySQL  (was: Forse InnoDB usage for MySQL)

> Force InnoDB usage for MySQL
> ----------------------------
>
>                 Key: AMBARI-18951
>                 URL: https://issues.apache.org/jira/browse/AMBARI-18951
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.4.2
>            Reporter: Myroslav Papirkovskyi
>            Assignee: Myroslav Papirkovskyi
>            Priority: Critical
>             Fix For: 2.5.0
>
>         Attachments: AMBARI-18951.patch
>
>
> We should always use InnoDB as database engine for MySQL as database with MyISAM engine cannot be upgraded properly.
> Key reason is that MyISAM doesn't store foreign keys information, but do store indexes with same name which lead to conflicts during upgrade.



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