You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Zhihua Deng (Jira)" <ji...@apache.org> on 2022/10/26 02:13:00 UTC
[jira] [Resolved] (HIVE-26629) Misleading error message with hive.metastore.limit.partition.request
[ https://issues.apache.org/jira/browse/HIVE-26629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Zhihua Deng resolved HIVE-26629.
--------------------------------
Fix Version/s: 4.0.0-alpha-2
Assignee: Zhihua Deng
Resolution: Fixed
> Misleading error message with hive.metastore.limit.partition.request
> ---------------------------------------------------------------------
>
> Key: HIVE-26629
> URL: https://issues.apache.org/jira/browse/HIVE-26629
> Project: Hive
> Issue Type: Bug
> Components: HiveServer2, Metastore
> Reporter: Miklos Szurap
> Assignee: Zhihua Deng
> Priority: Major
> Labels: pull-request-available
> Fix For: 4.0.0-alpha-2
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Dropping partitions from a table fails with a misleading error message saying that "partition not found":
> {code}
> 0: jdbc:hive2://nightly-71x-zx-1.nightly-71x-> alter table t1p drop partition (p1>0);
> Error: Error while compiling statement: FAILED: SemanticException [Error 10006]: Partition not found (p1 > 0) (state=42000,code=10006)
> {code}
> however the partitions exist, the real error message is visible in the HiveServer2 logs:
> {code}
> Caused by: MetaException(message:Number of partitions scanned (=2) on table 't1p' exceeds limit (=1). This is controlled on the metastore server by hive.metastore.limit.partition.request.)
> at org.apache.hadoop.hive.metastore.api.ThriftHiveMetastore$get_partitions_by_expr_result$get_partitions_by_expr_resultStandardScheme.read(ThriftHiveMetastore.java)
> ...
> {code}
> Hive should surface the real error message to the user, that the "hive.metastore.limit.partition.request" limit has been reached.
> This happens only when "hive.metastore.limit.partition.request" is set.
> Haven't verified other types of queries, potentially other queries fail similarly.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)