You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues-all@impala.apache.org by "Yu-Wen Lai (Jira)" <ji...@apache.org> on 2022/03/14 23:44:00 UTC

[jira] [Resolved] (IMPALA-10958) Decouple getConstraintsInformation from hive.ql.metadata.Table

     [ https://issues.apache.org/jira/browse/IMPALA-10958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Yu-Wen Lai resolved IMPALA-10958.
---------------------------------
    Fix Version/s: Impala 4.1.0
       Resolution: Fixed

> Decouple getConstraintsInformation from hive.ql.metadata.Table
> --------------------------------------------------------------
>
>                 Key: IMPALA-10958
>                 URL: https://issues.apache.org/jira/browse/IMPALA-10958
>             Project: IMPALA
>          Issue Type: Improvement
>          Components: Frontend
>            Reporter: Yu-Wen Lai
>            Assignee: Yu-Wen Lai
>            Priority: Major
>             Fix For: Impala 4.1.0
>
>
> After [HIVE-22782|http://issues.apache.org/jira/browse/HIVE-22782], ql.metadata.Table object has no methods to set PrimaryKeyInfo and ForeignKeyInfo alone. However, we call these two functions In DescribeResultFactory to set constraints and pass the table into HiveMetadataFormatUtils. Instead of calling the methods from table, we can directly pass PrimaryKeyInfo and ForeignKeyInfo to HiveMetadataFormatUtils so that Impala won't be influenced even though the table class changes interface.
> Additionally, we can get rid of ql.metadata.Table for getTableInformation altogether since it just needs metastore.api.Table internally.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org