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

Posted to issues@hive.apache.org by "Eugene Koifman (JIRA)" <ji...@apache.org> on 2017/10/02 19:01:00 UTC

[jira] [Assigned] (HIVE-17306) Support MySQL InnoDB Cluster

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

Eugene Koifman reassigned HIVE-17306:
-------------------------------------

    Assignee: Eugene Koifman

> Support MySQL InnoDB Cluster
> ----------------------------
>
>                 Key: HIVE-17306
>                 URL: https://issues.apache.org/jira/browse/HIVE-17306
>             Project: Hive
>          Issue Type: Improvement
>          Components: Transactions
>            Reporter: Shawn Weeks
>            Assignee: Eugene Koifman
>            Priority: Minor
>
> To support high availability of the Hive Metastore using a highly available database is required. To support the MySQL InnoDB Cluster it looks like we're just missing a couple primary keys as we were already using InnoDB tables for the metastore. It looks like it's primarily the transaction tables that don't have primary keys like TXN_COMPONENTS and COMPLETED_TXN_COMPONENTS. The primary keys can be surrogate sequences if there really is no unique identifier in these tables.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)