You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hive.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/06/12 22:50:00 UTC

[jira] [Updated] (HIVE-16520) Cache hive metadata in metastore

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

ASF GitHub Bot updated HIVE-16520:
----------------------------------
    Labels: TODOC3.0 pull-request-available  (was: TODOC3.0)

> Cache hive metadata in metastore
> --------------------------------
>
>                 Key: HIVE-16520
>                 URL: https://issues.apache.org/jira/browse/HIVE-16520
>             Project: Hive
>          Issue Type: New Feature
>          Components: Metastore
>            Reporter: Daniel Dai
>            Assignee: Daniel Dai
>            Priority: Major
>              Labels: TODOC3.0, pull-request-available
>             Fix For: 3.0.0
>
>         Attachments: HIVE-16520-1.patch, HIVE-16520-proto-2.patch, HIVE-16520-proto.patch, HIVE-16520.2.patch, HIVE-16520.3.patch, HIVE-16520.4.patch
>
>
> During Hive 2 benchmark, we find Hive metastore operation take a lot of time and thus slow down Hive compilation. In some extreme case, it takes much longer than the actual query run time. Especially, we find the latency of cloud db is very high and 90% of total query runtime is waiting for metastore SQL database operations. Based on this observation, the metastore operation performance will be greatly enhanced if we have a memory structure which cache the database query result.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)