[
https://issues.apache.org/jira/browse/HIVE-11527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15137936#comment-15137936
]
Jing Zhao commented on HIVE-11527:
----------------------------------
So IIUC, after replacing hdfs with webhdfs, the new URI will still be resolved
by FileSystem and finally a WebHdfsFileSystem instance will be created and
used? In that case, I think we can:
# If there is both hostname and port contained in the original hdfs URI, both
"hdfs" and port need to be replaced
# If there is no port in the original URI, this can be a logical URI (for
NameNode HA setup). Since WebHdfsFileSystem can also correctly handle logical
URI, replacing "hdfs" with "webhdfs" should be good enough
# It is also possible the URI only contains host name but no port, and the
default port will be loaded from configuration for either hdfs/webhdfs. In that
case replacing "hdfs" with "webhdfs" should also work.
> 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
> Attachments: HIVE-11527.WIP.patch
>
>
> 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
> Review board link: https://reviews.apache.org/r/40867
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
