[
https://issues.apache.org/jira/browse/HIVE-11527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15023428#comment-15023428
]
Vaibhav Gumashta commented on HIVE-11527:
-----------------------------------------
[~tasanuma0829] [~sershe] This approach makes sense to me. You could make a
small optimization by returning the hdfs uris as part of the ExecuteStatement
call, so that way in each of the FetchResults (HiveQueryResultSet#next) call to
HS2, you won't need to send the uris over the wire.
> bypass HiveServer2 thrift interface for query results
> -----------------------------------------------------
>
> Key: HIVE-11527
> URL: https://issues.apache.org/jira/browse/HIVE-11527
> Project: Hive
> Issue Type: Improvement
> Components: HiveServer2
> Reporter: Sergey Shelukhin
> Assignee: Takanobu Asanuma
>
> Right now, HS2 reads query results and returns them to the caller via its
> thrift API.
> There should be an option for HS2 to return some pointer to results (an HDFS
> link?) and for the user to read the results directly off HDFS inside the
> cluster, or via something like WebHDFS outside the cluster
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
