hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hive QA (JIRA)" <>
Subject [jira] [Commented] (HIVE-18661) CachedStore: Use metastore notification log events to update cache
Date Fri, 14 Dec 2018 09:39:00 GMT


Hive QA commented on HIVE-18661:

Here are the results of testing the latest attachment:

{color:red}ERROR:{color} -1 due to build exiting with an error

Test results:
Console output:
Test logs:

Executing org.apache.hive.ptest.execution.TestCheckPhase
Tests exited with: Exception: Patch URL
was found in seen patch url's cache and a test was probably run already on it. Aborting...

This message is automatically generated.

ATTACHMENT ID: 12951781 - PreCommit-HIVE-Build

> CachedStore: Use metastore notification log events to update cache
> ------------------------------------------------------------------
>                 Key: HIVE-18661
>                 URL:
>             Project: Hive
>          Issue Type: Sub-task
>          Components: Metastore
>            Reporter: Vaibhav Gumashta
>            Assignee: mahesh kumar behera
>            Priority: Major
>              Labels: pull-request-available
>         Attachments: HIVE-18661.02.patch, HIVE-18661.03.patch, HIVE-18661.04.patch, HIVE-18661.05.patch,
HIVE-18661.06.patch, HIVE-18661.07.patch, HIVE-18661.08.patch, HIVE-18661.09.patch
> Currently, a background thread updates the entire cache which is pretty inefficient.
We capture the updates to metadata in NOTIFICATION_LOG table which is getting used in the
Replication work. We should have the background thread apply these notifications to incrementally
update the cache.

This message was sent by Atlassian JIRA

View raw message