@Shab no, those warn messages are not related. Did you try setting 'hive.metastore.client.socket.timeout' value to, 5 mins, under the "Service Monitor Client Config Overrides" in Hive configuration?   We can completely disable Hive metastore canary, but I won't advise that. if Hive is working as expected, we could safely ignore these canary warnings, however, try setting the  aforementioned socket timeout parameter, and that could help the canary tests perform without fail.   If you use Sentry in your cluster, sometimes it blocks HMS, which in turn affects Metastore Canary. You could add the following property to overcome that.   Navigate to Cloudera Manager > Hive > Configuration > "Hive Metastore Server Advanced Configuration Snippet (Safety Valve) for hive-site.xml" > add the following: <property> <name>hive.metastore.event.listeners</name> <description>This will stop HMS blocking by Sentry</description> <value></value> </property>   ... View more

@hxn It seems like hive on Tez service is not up. Please go through Hive on Tez logs, and you should see more info around the error 'Error stopping schq'. We need to bring Hive service up first, and then we can approach the Hue issue, or Hue might start working after fixing Hive. ... View more

@sat_046 Please refer to the Cloudera doc on Starting and stopping services. ... View more

@Anitauzanna you could do it exactly the same way. e.g. CREATE TABLE final_table(col1 int, col3 int) PARTITIONED BY (year int, month int, day int) stored as orc;   INSERT OVERWRITE TABLE final_table PARTITION(year,month,day) select col1, col3, substring(col2,1,4), substring(col2,5,6), substring(col2,7,8) from orig_table; ... View more