[
https://issues.apache.org/jira/browse/HIVE-18661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16721102#comment-16721102
]
Hive QA commented on HIVE-18661:
--------------------------------
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12951781/HIVE-18661.09.patch
{color:red}ERROR:{color} -1 due to build exiting with an error
Test results:
https://builds.apache.org/job/PreCommit-HIVE-Build/15319/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/15319/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-15319/
Messages:
{noformat}
Executing org.apache.hive.ptest.execution.TestCheckPhase
Tests exited with: Exception: Patch URL
https://issues.apache.org/jira/secure/attachment/12951781/HIVE-18661.09.patch
was found in seen patch url's cache and a test was probably run already on it.
Aborting...
{noformat}
This message is automatically generated.
ATTACHMENT ID: 12951781 - PreCommit-HIVE-Build
> CachedStore: Use metastore notification log events to update cache
> ------------------------------------------------------------------
>
> Key: HIVE-18661
> URL: https://issues.apache.org/jira/browse/HIVE-18661
> 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
(v7.6.3#76005)
