[
https://issues.apache.org/jira/browse/SPARK-22121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16180024#comment-16180024
]
Apache Spark commented on SPARK-22121:
--------------------------------------
User 'squito' has created a pull request for this issue:
https://github.com/apache/spark/pull/19343
> 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: [email protected]
For additional commands, e-mail: [email protected]
