hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Amruth S (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-18338) [Client, JDBC] Asynchronous interface through hive JDBC.
Date Mon, 25 Dec 2017 15:29:00 GMT

    [ https://issues.apache.org/jira/browse/HIVE-18338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16303307#comment-16303307
] 

Amruth S commented on HIVE-18338:
---------------------------------

Travis CI seem to have failed in the PR? Is this a problem? Please let me know.

> [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
>              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
HiveStatement.java.



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

Mime
View raw message