[HIVE-13608] We should provide better error message while constraints with duplicate names are created

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0.0
• Fix Version/s: 2.1.0
• Component/s: Diagnosability, Metastore
• Target Version/s: 2.1.0
• Assignee: Hari Sankar Sivarama Subramaniyan
• Reporter: Hari Sankar Sivarama Subramaniyan
• Created: 25/Apr/16 21:12
• Updated: 19/Jul/16 00:23
• Resolved: 17/May/16 20:43

Description

PREHOOK: query: create table t1(x int, constraint pk1 primary key (x) disable novalidate)
PREHOOK: type: CREATETABLE
PREHOOK: Output: database:default
PREHOOK: Output: default@t1
POSTHOOK: query: create table t1(x int, constraint pk1 primary key (x) disable novalidate)
POSTHOOK: type: CREATETABLE
POSTHOOK: Output: database:default
POSTHOOK: Output: default@t1
PREHOOK: query: create table t2(x int, constraint pk1 primary key (x) disable novalidate)
PREHOOK: type: CREATETABLE
PREHOOK: Output: database:default
PREHOOK: Output: default@t2
FAILED: Execution Error, return code 1 from org.apache.hadoop.hive.ql.exec.DDLTask. MetaException(message:For direct MetaStore DB connections, we don't support retries at the client level.)

In the above case, it seems like useful error message is lost. It looks like a generic problem with metastore server/client exception handling and message propagation. Seems like exception parsing logic of RetryingMetaStoreClient::invoke() needs to be updated.

Issue Links

• blocks: HIVE-13618 Trailing spaces in partition column will be treated differently
• is duplicated by: HIVE-11918 Implement/Enable constant related optimization rules in Calcite
• is related to: HIVE-13290 Support primary keys/foreign keys constraint as part of create table command in Hive