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

ASF GitHub Bot logged work on HIVE-22015:
-----------------------------------------

                Author: ASF GitHub Bot
            Created on: 03/Jul/20 09:38
            Start Date: 03/Jul/20 09:38
    Worklog Time Spent: 10m 
      Work Description: adesh-rao commented on a change in pull request #1109:
URL: https://github.com/apache/hive/pull/1109#discussion_r449486010



##########
File path: 
standalone-metastore/metastore-server/src/main/java/org/apache/hadoop/hive/metastore/cache/SharedCache.java
##########
@@ -1788,6 +2082,58 @@ public void addPartitionToCache(String catName, String 
dbName, String tblName, P
     }
   }
 
+  public void addPrimaryKeysToCache(String catName, String dbName, String 
tblName, List<SQLPrimaryKey> keys) {
+    try {
+      cacheLock.readLock().lock();

Review comment:
       This is fine, the below method (cachePrimaryKeys), takes the writeLock. 
the read lock here, is just to get the tblWrapper object.




----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


Issue Time Tracking
-------------------

    Worklog Id:     (was: 454344)
    Time Spent: 1h 50m  (was: 1h 40m)

> [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: 1h 50m
>  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)

Reply via email to