Imran Rashid created SPARK-22121: ------------------------------------ Summary: Spark should fix hive table location for hdfs HA Key: SPARK-22121 URL: https://issues.apache.org/jira/browse/SPARK-22121 Project: Spark Issue Type: Improvement Components: SQL Affects Versions: 2.2.0 Reporter: Imran Rashid Assignee: Imran Rashid
When converting an existing hdfs setup to have multiple namenodes, users *should* run the hive metatool to change the location of the metastore, to refer to the nameservice, instead of a specific namenode. (See the {{updateLocation}} section of the [metatool docs|https://cwiki.apache.org/confluence/display/Hive/Hive+MetaTool].) However, users tend to forget to do this. If hdfs HA is turned on after a hive database is already created, the db location may still reference just one namenode, instead of the nameservice. To be a little more user friendly, Spark should detect the misconfiguration and try to auto-adjust for it. (This is the behavior from hive as well.) -- This message was sent by Atlassian JIRA (v6.4.14#64029) --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org