You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Karthik Manamcheri (JIRA)" <ji...@apache.org> on 2018/09/27 23:45:00 UTC
[jira] [Commented] (SPARK-25561) HiveClient.getPartitionsByFilter
throws an exception if Hive retries directSql
[ https://issues.apache.org/jira/browse/SPARK-25561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16631193#comment-16631193 ]
Karthik Manamcheri commented on SPARK-25561:
--------------------------------------------
The root cause was from SPARK-17992 ping [~michael] what are your thoughts on this?
> HiveClient.getPartitionsByFilter throws an exception if Hive retries directSql
> ------------------------------------------------------------------------------
>
> Key: SPARK-25561
> URL: https://issues.apache.org/jira/browse/SPARK-25561
> Project: Spark
> Issue Type: Bug
> Components: SQL
> Affects Versions: 2.1.0
> Reporter: Karthik Manamcheri
> Priority: Major
>
> In HiveShim.scala, the current behavior is that if hive.metastore.try.direct.sql is enabled, we expect the getPartitionsByFilter call to succeed. If it fails, we'll throw a RuntimeException.
> However, this might not always be the case. Hive's direct SQL functionality is best-attempt. Meaning, it will fall back to ORM if direct sql fails. Spark should handle that exception correctly if Hive falls back to ORM.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org