hive-issues mailing list archives

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

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

Adesh Kumar Rao commented on HIVE-22015:
----------------------------------------

[~anishek] [~thejas] 
 While working on adding foreign keys in cached store from notification logs, I realized that
DBNotificationListener is trying to process ForeignKey constraint based on PKTable instead
of FKTable [here|https://github.com/apache/hive/blob/48c01107cd18d80867369e5addfa1fc5b4e7f698/hcatalog/server-extensions/src/main/java/org/apache/hive/hcatalog/listener/DbNotificationListener.java#L658].
Shouldn't it be logically added based on the foreign key db and table instead? 
 
cc [~kishendas]

> [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
>
> 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