hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (HIVE-18338) [Client, JDBC] Asynchronous interface through hive JDBC.
Date Mon, 25 Dec 2017 13:31:05 GMT


ASF GitHub Bot commented on HIVE-18338:

GitHub user amrk7s opened a pull request:

    HIVE-18338 Exposing asynchronous execution through hive-jdbc client

    **Problem statement**
    Hive JDBC currently exposes 2 methods related to asynchronous execution
    **executeAsync()** - to trigger a query execution and return immediately.
    **waitForOperationToComplete()** - which waits till the current execution is complete
**blocking the user thread**. 
    This has one problem
    - If the client process goes down, there is no way to resume queries although hive server
is completely asynchronous. 
    If operation handle could be exposed, we can latch on to an active execution of a query.
    **Code changes**
    Operation handle is exposed. So client can keep a copy.
    latchSync() and latchAsync() methods take an operation handle and try to latch on to the
current execution in hive server if present

You can merge this pull request into a Git repository by running:

    $ git pull async_jdbc

Alternatively you can review and apply these changes as the patch at:

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #284
commit 9afa0ae9a9e2c38be3fbdadab230fdd399ab8e5b
Author: amrk7s <amruth.s@...>
Date:   2017-12-25T13:20:22Z

    HIVE-18338 Exposing asynchronous execution through hive-jdbc client


> [Client, JDBC] Asynchronous 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
> Lot of users are struggling and rewriting a lot of boiler plate over thrift to get pure
asynchronous capability. 
> The idea is to expose operation handle, so that clients can persist it and later can
latch on to the same execution.
> Let me know your ideas around this. We have solved this already at our org by tweaking

This message was sent by Atlassian JIRA

View raw message