Uploaded image for project: 'Hive'
  1. Hive
  2. HIVE-17306

Support MySQL InnoDB Cluster

Log workAgile BoardRank to TopRank to BottomAdd voteVotersWatch issueWatchersCreate sub-taskConvert to sub-taskMoveLinkCloneLabelsUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Open
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Transactions
    • Labels:
      None

      Description

      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.

        Attachments

          Activity

          $i18n.getText('security.level.explanation', $currentSelection) Viewable by All Users
          Cancel

            People

              Dates

              • Created:
                Updated:

                Issue deployment