[
https://issues.apache.org/jira/browse/SPARK-13984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15202191#comment-15202191
]
Rekha Joshi commented on SPARK-13984:
-------------------------------------
Hi [~Jianfeng Hu] Implicitly modifying schema is disabled by default in hive.As
you have set schema.verification to true, it first checks hive binaries is
compatible with metastore schema version.If not it raises this error.You can
set hive.metastore.schema.verification to false, to suppress this check., and
let metastore implicitly modify the schema.Anyhow related to hive itself.
It is not a Spark issue.If you and [~srowen] agree, this can be closed.thanks.
> Schema verification always fail when using remote Hive metastore
> ----------------------------------------------------------------
>
> Key: SPARK-13984
> URL: https://issues.apache.org/jira/browse/SPARK-13984
> Project: Spark
> Issue Type: Bug
> Components: SQL
> Affects Versions: 1.6.1
> Reporter: Jianfeng Hu
>
> Launch a Hive metastore Thrift server, and then in hive-site.xml:
> - set hive.metastore.uris
> - set hive.metastore.schema.verification to true
> Run spark-shell, it will fail with:
> java.lang.RuntimeException: Unable to instantiate
> org.apache.hadoop.hive.ql.metadata.SessionHiveMetaStoreClient
> Caused by: MetaException(message:Version information not found in metastore.
> It might be using the wrong metastore (could be possibly the local derby
> metastore) when doing the verification? Not exactly sure on this but maybe
> could someone more familiar with the HiveContext code help investigating?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
