hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hive QA (JIRA)" <>
Subject [jira] [Commented] (HIVE-14778) document threading model of Streaming API
Date Fri, 16 Sep 2016 23:40:21 GMT


Hive QA commented on HIVE-14778:

Here are the results of testing the latest attachment:

{color:red}ERROR:{color} -1 due to no test(s) being added or modified.

{color:red}ERROR:{color} -1 due to 9 failed/errored test(s), 10527 tests executed
*Failed tests:*

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

This message is automatically generated.

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

> document threading model of Streaming API
> -----------------------------------------
>                 Key: HIVE-14778
>                 URL:
>             Project: Hive
>          Issue Type: Bug
>          Components: HCatalog, Transactions
>    Affects Versions: 0.14.0
>            Reporter: Eugene Koifman
>            Assignee: Eugene Koifman
>         Attachments: HIVE-14778.patch
>   Original Estimate: 1h
>  Remaining Estimate: 1h
> The model is not obvious and needs to be documented properly.
> A StreamingConnection internally maintains 2 MetaStoreClient objects (each has 1 Thrift
client for actual RPC). Let's call them "primary" and "heartbeat". Each TransactionBatch created
from a given StreamingConnection, gets a reference to both of these MetaStoreClients. 
> So the model is that there is at most 1 outstanding (not closed) TransactionBatch for
any given StreamingConnection and for any given TransactionBatch there can be at most 2 threads
accessing it concurrently. 1 thread calling TransactionBatch.heartbeat() (and nothing else)
and the other calling all other methods.

This message was sent by Atlassian JIRA

View raw message