[
https://issues.apache.org/jira/browse/HIVE-24257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17213897#comment-17213897
]
Sankar Hariappan commented on HIVE-24257:
-----------------------------------------
[~ashish-kumar-sharma],
I think, this change breaks the backward compatibility and HMS client interface
will be impacted. We cannot change it now.
> Wrong check constraint naming in Hive metastore
> -----------------------------------------------
>
> Key: HIVE-24257
> URL: https://issues.apache.org/jira/browse/HIVE-24257
> Project: Hive
> Issue Type: Bug
> Components: Standalone Metastore
> Reporter: Ashish Sharma
> Assignee: Ashish Sharma
> Priority: Trivial
> Labels: pull-request-available
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Current
> struct SQLCheckConstraint {
> 1: string catName, // catalog name
> 2: string table_db, // table schema
> 3: string table_name, // table name
> 4: string column_name, // column name
> 5: string check_expression,// check expression
> 6: string dc_name, // default name
> 7: bool enable_cstr, // Enable/Disable
> 8: bool validate_cstr, // Validate/No validate
> 9: bool rely_cstr // Rely/No Rely
> }
> Naming for CheckConstraint is wrong it should be cc_name instead of dc_name
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
