You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Amruth S (JIRA)" <ji...@apache.org> on 2017/12/25 05:40:00 UTC
[jira] [Updated] (HIVE-18338) [Client, JDBC] Asynchronous interface
through hive JDBC.
[ https://issues.apache.org/jira/browse/HIVE-18338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Amruth S updated HIVE-18338:
----------------------------
Affects Version/s: 2.3.2
Status: Patch Available (was: Open)
> [Client, JDBC] Asynchronous 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
>
> 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)