hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From amrk7s <...@git.apache.org>
Subject [GitHub] hive pull request #284: HIVE-18338 Exposing asynchronous execution through h...
Date Mon, 25 Dec 2017 13:30:04 GMT
GitHub user amrk7s opened a pull request:

    https://github.com/apache/hive/pull/284

    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. 
    
    **Proposal**
    
    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 https://github.com/Flipkart/hive async_jdbc

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

    https://github.com/apache/hive/pull/284.patch

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

----


---

Mime
View raw message