@Michael Grabenstein Could you try running the query after setting property tez.runtime.shuffle.ssl.enable=false and let us know the result? ... View more

@Varun Singh Are you trying to redirect the output of Hive logging from console? Refer Hive logging. ... View more

@Varun Singh Try launching the beeline command as "beeline --silent=true". ... View more

@Anish Kumar The issue might be related to Jira HIVE-7711. Try setting `hive.plan.serialization.format=javaXML` and try running shell script again. ... View more

@mÁRIO Rodrigues Refer to blog for details ... View more

@Santhosh B Gowda This is more of a design on how JDBC client needs to be configured with the principal name of HIVESERVER2 to make sure the auth type to be Kerberos. Also, the authentication token would for the user who has valid kerberos ticket while connecting from Beeline. For example, kinit example_user@EXAMPLE.COM jdbc:hive2://zkhost:2181/db;serviceDiscoveryMode=zooKeeper;zooKeeperNamespace=hiveserver2;principal=hive/_HOST@EXAMPLE.COM; In this case, the authentication against the KDC would be for user example_user and the auth header would have KERBEROS by specifying the principal of Hiveserver2. ... View more

@Joshua Adeleke Issue is related to MySQL limitation. Refer to below links to resolve the same: https://confluence.atlassian.com/fishkb/mysql-database-migration-fails-with-specified-key-was-too-long-max-key-length-is-1000-bytes-298978735.html http://dba.stackexchange.com/questions/76567/how-to-resolve-specified-key-was-too-long-max-key-length-is-767-bytes ... View more