[ 
https://issues.apache.org/jira/browse/HIVE-17306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17270383#comment-17270383
 ] 

Frédéric Descamps commented on HIVE-17306:
------------------------------------------

More info about this feature in this article: 
https://lefred.be/content/mysql-invisible-column-part-iii/

> 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: Steve Yeom
>            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
(v8.3.4#803005)

Reply via email to