[jira] [Updated] (HIVE-18338) [Client, JDBC] Expose async interface through hive JDBC.

["Amruth S (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HIVE-18338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Amruth S updated HIVE-18338:
----------------------------
    Summary: [Client, JDBC] Expose async interface through hive JDBC.  (was: [Client, JDBC] Asynchronous interface through hive JDBC.)

> [Client, JDBC] Expose async interface through hive JDBC.
> --------------------------------------------------------
>
>                 Key: HIVE-18338
>                 URL: https://issues.apache.org/jira/browse/HIVE-18338
>             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
>
>
> 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 HiveStatement.java.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)