hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anishek Agarwal (Jira)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-22015) [CachedStore] Cache table constraints in CachedStore
Date Mon, 15 Jun 2020 10:41:00 GMT

    [ https://issues.apache.org/jira/browse/HIVE-22015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17135733#comment-17135733
] 

Anishek Agarwal commented on HIVE-22015:
----------------------------------------

The constraint is created on the from table (Primary) and not target table(foreign). For ex
if there is foreign key relationship from t1 - > t2 the relation ship is stored as part
of t1 definition not as part of t2, hence the event will be generated for the primary key
table and DB.



> [CachedStore] Cache table constraints in CachedStore
> ----------------------------------------------------
>
>                 Key: HIVE-22015
>                 URL: https://issues.apache.org/jira/browse/HIVE-22015
>             Project: Hive
>          Issue Type: Sub-task
>            Reporter: Daniel Dai
>            Assignee: Adesh Kumar Rao
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> Currently table constraints are not cached. Hive will pull all constraints from tables
involved in query, which results multiple db reads (including get_primary_keys, get_foreign_keys,
get_unique_constraints, etc). The effort to cache this is small as it's just another table
component.



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

Mime
View raw message