Miklos Szurap created HIVE-26629:
------------------------------------
Summary: 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
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)
