hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eugene Koifman (JIRA)" <>
Subject [jira] [Assigned] (HIVE-17306) Support MySQL InnoDB Cluster
Date Mon, 02 Oct 2017 19:01:00 GMT


Eugene Koifman reassigned HIVE-17306:

    Assignee: Eugene Koifman

> Support MySQL InnoDB Cluster
> ----------------------------
>                 Key: HIVE-17306
>                 URL:
>             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

This message was sent by Atlassian JIRA

View raw message