hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hive QA (JIRA)" <>
Subject [jira] [Commented] (HIVE-13725) ACID: Streaming API should synchronize calls when multiple threads use the same endpoint
Date Sun, 26 Jun 2016 20:00:53 GMT


Hive QA commented on HIVE-13725:

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 4 failed/errored test(s), 10255 tests executed
*Failed tests:*
- did not produce a TEST-*.xml file

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: 4 tests failed

This message is automatically generated.

ATTACHMENT ID: 12813561 - PreCommit-HIVE-MASTER-Build

> ACID: Streaming API should synchronize calls when multiple threads use the same endpoint
> ----------------------------------------------------------------------------------------
>                 Key: HIVE-13725
>                 URL:
>             Project: Hive
>          Issue Type: Bug
>          Components: HCatalog, Metastore, Transactions
>    Affects Versions: 1.2.1, 2.0.0
>            Reporter: Vaibhav Gumashta
>            Assignee: Vaibhav Gumashta
>            Priority: Critical
>              Labels: ACID, Streaming
>         Attachments: HIVE-13725.1.patch, HIVE-13725.2.patch, HIVE-13725.3.patch, HIVE-13725.4.patch,
HIVE-13725.5.patch, addendum.txt
> Currently, the streaming endpoint creates a metastore client which gets used for RPC.
The client itself is not internally thread safe. Therefore, the API methods should provide
the relevant synchronization so that the methods can be called from different threads. A sample
use case is as follows:
> 1. Thread 1 creates a streaming endpoint and opens a txn batch.
> 2. Thread 2 heartbeats the txn batch.
> With the current impl, this can result in an "out of sequence response", since the response
of the calls in thread1 might end up going to thread2 and vice-versa.

This message was sent by Atlassian JIRA

View raw message