[
https://issues.apache.org/jira/browse/AMBARI-18951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15702547#comment-15702547
]
Hudson commented on AMBARI-18951:
---------------------------------
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6091 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/6091/])
AMBARI-18951. Force InnoDB usage for MySQL. (mpapirkovskyy) (mpapyrkovskyy:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=255725dfc07a4a4fd7fc8b3f6cdbd7cced1c375a])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/upgrade/SchemaUpgradeHelper.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/orm/helpers/dbms/MySqlHelper.java
* (edit) ambari-server/src/main/resources/Ambari-DDL-MySQL-CREATE.sql
> 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)
