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

Posted to issues@impala.apache.org by "Anurag Mantripragada (Jira)" <ji...@apache.org> on 2020/02/16 20:34:00 UTC

[jira] [Resolved] (IMPALA-9256) Refactor constraint information into a separate class.

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

Anurag Mantripragada resolved IMPALA-9256.
------------------------------------------
    Fix Version/s: Impala 3.4.0
       Resolution: Fixed

> Refactor constraint information into a separate class.
> ------------------------------------------------------
>
>                 Key: IMPALA-9256
>                 URL: https://issues.apache.org/jira/browse/IMPALA-9256
>             Project: IMPALA
>          Issue Type: Sub-task
>          Components: Frontend
>            Reporter: Anurag Mantripragada
>            Assignee: Anurag Mantripragada
>            Priority: Major
>             Fix For: Impala 3.4.0
>
>
> We recently added support for primary keys and foreign keys information for tables. However, it is cleaner to have an SQLConstraint class as a container for these constraints just like hive does here: [https://github.com/apache/hive/blob/master/ql/src/java/org/apache/hadoop/hive/ql/ddl/table/constraint/Constraints.java.|https://github.com/apache/hive/blob/master/ql/src/java/org/apache/hadoop/hive/ql/ddl/table/constraint/Constraints.java]
> This can be extended to support other kinds of constraints in the future.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)