hive-issues mailing list archives

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

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

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

                Author: ASF GitHub Bot
            Created on: 15/Jun/20 10:31
            Start Date: 15/Jun/20 10:31
    Worklog Time Spent: 10m 
      Work Description: adesh-rao commented on pull request #1109:
URL: https://github.com/apache/hive/pull/1109#issuecomment-644046296


   This patch doesn't add caching for default/unique constraints as they are aren't pushed
to notification logs. I have opened a jira for the same: HIVE-23618.
   
   I will add unique/default constraints as part of separate jira once HIVE-23618 is resolved.


----------------------------------------------------------------
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:
users@infra.apache.org


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

    Worklog Id:     (was: 445769)
    Time Spent: 20m  (was: 10m)

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