hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Drome (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-4166) closeAllForUGI causes failure in hiveserver2 when fetching large amount of data
Date Thu, 14 Mar 2013 00:52:16 GMT

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

Chris Drome commented on HIVE-4166:
-----------------------------------

[~prasadm] thanks for the comment. We are working with a patched version of 0.10, but I will
keep this in mind.

The original code assumed it was okay to close all FileSystem resources at the end of each
call to process, with HiveServer2 this assumption no longer holds. So it should be fixed to
ensure that doAs works properly or doAs should be deprecated in favor of impersonation.
                
> closeAllForUGI causes failure in hiveserver2 when fetching large amount of data
> -------------------------------------------------------------------------------
>
>                 Key: HIVE-4166
>                 URL: https://issues.apache.org/jira/browse/HIVE-4166
>             Project: Hive
>          Issue Type: Bug
>          Components: Security, Shims
>    Affects Versions: 0.10.0, 0.11.0
>            Reporter: Chris Drome
>            Assignee: Chris Drome
>         Attachments: HIVE-4166-0.10.patch, HIVE-4166-trunk.patch
>
>
> HiveServer2 configured to use Kerberos authentication with doAs enabled throws an exception
when fetching a large amount of data from a query.
> The exception is caused because FileSystem.closeAllForUGI is always called at the end
of TUGIAssumingProcessor.process. This affects requests on the ResultSet for data from a SELECT
query when the amount of data exceeds a certain size. At that point any subsequent calls to
fetch more data throw an exception because the underlying DFSClient has been closed.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message