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

Support UTF8 in MySQL Metastore Backend

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Open
    • Major
    • Resolution: Unresolved
    • 2.4.0, 3.0.0
    • None
    • None

    Description

      hive-schema-2.2.0.mysql.sql
      CREATE TABLE IF NOT EXISTS `COLUMNS_V2` (
        `CD_ID` bigint(20) NOT NULL,
        `COMMENT` varchar(256) CHARACTER SET latin1 COLLATE latin1_bin DEFAULT NULL,
        `COLUMN_NAME` varchar(767) CHARACTER SET latin1 COLLATE latin1_bin NOT NULL,
        `TYPE_NAME` varchar(4000) DEFAULT NULL,
        `INTEGER_IDX` int(11) NOT NULL,
        PRIMARY KEY (`CD_ID`,`COLUMN_NAME`),
        KEY `COLUMNS_V2_N49` (`CD_ID`),
        CONSTRAINT `COLUMNS_V2_FK1` FOREIGN KEY (`CD_ID`) REFERENCES `CDS` (`CD_ID`)
      ) ENGINE=InnoDB DEFAULT CHARSET=latin1;
      

      Hive explicitly defines a CHARACTER SET latin1 COLLATE latin1_bin in the schema design. This explicit definition should either be removed, so that it can fallback onto the database administrator's defaults, or changed to CHARACTER SET utf8 COLLATE utf8_bin to change the explicit definition to utf8.

      This will allow Hive to support UTF8 characters in MySQL backend databases for our international friends.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              belugabehr David Mollitor
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

                Created:
                Updated: