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 "Shant Hovsepian (Jira)" <ji...@apache.org> on 2020/07/18 20:03:00 UTC

[jira] [Updated] (IMPALA-9971) Use defined table constraints during query planning

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

Shant Hovsepian updated IMPALA-9971:
------------------------------------
    Summary: Use defined table constraints during query planning  (was: Use defined tabled constraints during query planning)

> Use defined table constraints during query planning
> ---------------------------------------------------
>
>                 Key: IMPALA-9971
>                 URL: https://issues.apache.org/jira/browse/IMPALA-9971
>             Project: IMPALA
>          Issue Type: New Feature
>          Components: Frontend
>            Reporter: Shant Hovsepian
>            Priority: Major
>
> With the implementation of [IMPALA-3531|https://issues.apache.org/jira/browse/IMPALA-3531] the planner now has access to defined table constraints. The Hive metastore supports defining nullability, uniquness, and referential integrity constraints. This metadata should be used for more effective query planning.



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

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