hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hive QA (JIRA)" <>
Subject [jira] [Commented] (HIVE-18338) [Client, JDBC] Expose async interface through hive JDBC.
Date Mon, 20 May 2019 20:32:00 GMT


Hive QA commented on HIVE-18338:

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), 16059 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.YetusPhase
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: 12969189 - PreCommit-HIVE-Build

> [Client, JDBC] Expose async interface through hive JDBC.
> --------------------------------------------------------
>                 Key: HIVE-18338
>                 URL:
>             Project: Hive
>          Issue Type: Improvement
>          Components: Clients, JDBC
>    Affects Versions: 2.3.2
>            Reporter: Amruth S
>            Assignee: Amruth S
>            Priority: Minor
>              Labels: pull-request-available
>         Attachments: HIVE-18338.patch, HIVE-18338.patch.1, HIVE-18338.patch.2, HIVE-18338.patch.3,
> This exposes async API in HiveStatement (jdbc module)
> The JDBC interface always have had strict synchronous APIs. 
> So the hive JDBC implementation also had to follow it though the hive server is fully
> Developers trying to build proxies on top of hive servers end up writing thrift client
from scratch to make it asynchronous and robust to its restarts.
> The common pattern is
>  # Submit query, get operation handle and store in a persistent store
>  # Poll and wait for completion
>  # Stream results
>  # In the event of restarts, restore OperationHandle from persistent store and continue
> The patch does 2 things
>  * exposes operation handle (once a query is submitted) {{getOperationhandle()}} 
> Developers can persist this along with the actual hive server url {{getJdbcUrl}}
>  * latch APIs 
> Developers can create a statement and latch on to an operation handle that was persisted
earlier. For latch, the statement should be created from the actual hive server URI connection
in which the query was submitted.

This message was sent by Atlassian JIRA

View raw message