Home Forums HDP on Linux – Installation Hive check execute failed HDP1.3

This topic contains 1 reply, has 1 voice, and was last updated by  Kobi Attia 9 months, 4 weeks ago.

  • Creator
    Topic
  • #41876

    Kobi Attia
    Participant

    Hi

    I ran the installation of cluster in ambari, everything was installed correctly until the point “Hive check execute”, I get this Error:
    .
    .
    .
    notice: /Stage[2]/Hdp-hcat::Hcat::Service_check/Exec[hcatSmoke.sh prepare]/returns: SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
    notice: /Stage[2]/Hdp-hcat::Hcat::Service_check/Exec[hcatSmoke.sh prepare]/returns: SLF4J: Actual binding is of type [org.slf4j.impl.Log4jLoggerFactory]
    notice: /Stage[2]/Hdp-hcat::Hcat::Service_check/Exec[hcatSmoke.sh prepare]/returns: FAILED: Execution Error, return code 1 from org.apache.hadoop.hive.ql.exec.DDLTask. MetaException(message:javax.jdo.JDODataStoreException: An exception was thrown while adding/validating class(es) : Specified key was too long; max key length is 767 bytes
    notice: /Stage[2]/Hdp-hcat::Hcat::Service_check/Exec[hcatSmoke.sh prepare]/returns: com.mysql.jdbc.exceptions.MySQLSyntaxErrorException: Specified key was too long; max key length is 767 bytes
    notice: /Stage[2]/Hdp-hcat::Hcat::Service_check/Exec[hcatSmoke.sh prepare]/returns: at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:936)
    notice: /Stage[2]/Hdp-hcat::Hcat::Service_check/Exec[hcatSmoke.sh prepare]/returns: at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:2985)
    notice: /Stage[2]/Hdp-hcat::Hcat::Service_check/Exec[hcatSmoke.sh prepare]/returns: at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1631)
    notice: /Stage[2]/Hdp-hcat::Hcat::Service_check/Exec[hcatSmoke.sh prepare]/returns: at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:1723)
    .
    .
    .

    Thank for any help!

    Kobi

Viewing 1 replies (of 1 total)

The topic ‘Hive check execute failed HDP1.3’ is closed to new replies.

  • Author
    Replies
  • #42228

    Kobi Attia
    Participant

    Hi

    Problem: Hive throws above exception when old version of MySQL is used as hive metastore.

    Solution: Set Latin1 as the charset for metastore
    mysql> alter database metastore character set latin1.

    Thanks

    Collapse
Viewing 1 replies (of 1 total)