hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hive QA (JIRA)" <>
Subject [jira] [Commented] (HIVE-16520) Cache hive metadata in metastore
Date Mon, 01 May 2017 20:34:04 GMT


Hive QA commented on HIVE-16520:

Here are the results of testing the latest attachment:

{color:green}SUCCESS:{color} +1 due to 1 test(s) being added or modified.

{color:red}ERROR:{color} -1 due to 2 failed/errored test(s), 10631 tests executed
*Failed tests:*
org.apache.hadoop.hive.cli.TestAccumuloCliDriver.testCliDriver[accumulo_index] (batchId=225)
org.apache.hadoop.hive.cli.TestMiniLlapLocalCliDriver.testCliDriver[vector_if_expr] (batchId=143)

Test results:
Console output:
Test logs:

Executing org.apache.hive.ptest.execution.TestCheckPhase
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
Tests exited with: TestsFailedException: 2 tests failed

This message is automatically generated.

ATTACHMENT ID: 12865806 - PreCommit-HIVE-Build

> Cache hive metadata in metastore
> --------------------------------
>                 Key: HIVE-16520
>                 URL:
>             Project: Hive
>          Issue Type: New Feature
>          Components: Metastore
>            Reporter: Daniel Dai
>            Assignee: Daniel Dai
>         Attachments: HIVE-16520-1.patch, HIVE-16520.2.patch, HIVE-16520.3.patch, HIVE-16520.4.patch,
HIVE-16520-proto-2.patch, HIVE-16520-proto.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

View raw message