[jira] [Commented] (HIVE-6484) HiveServer2 doAs should be session aware both for secured and unsecured session implementation.

2014-02-25 Thread Vaibhav Gumashta (JIRA)

[ 
https://issues.apache.org/jira/browse/HIVE-6484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13911522#comment-13911522
 ] 

Vaibhav Gumashta commented on HIVE-6484:


[~navis]: Thanks for linking! That jira had slipped out of my radar. 

 HiveServer2 doAs should be session aware both for secured and unsecured 
 session implementation.
 ---

 Key: HIVE-6484
 URL: https://issues.apache.org/jira/browse/HIVE-6484
 Project: Hive
  Issue Type: Improvement
  Components: HiveServer2
Affects Versions: 0.13.0
Reporter: Vaibhav Gumashta
Assignee: Vaibhav Gumashta
 Fix For: 0.13.0


 Currently in unsecured case, the doAs is performed by decorating 
 TProcessor.process method. This has been causing cleanup issues as we end up 
 creating a new clientUgi for each request rather than for each session. This 
 also cleans up the code.
 [~thejas] Probably you can add more if you've seen other issues related to 
 this.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)


[jira] [Commented] (HIVE-6484) HiveServer2 doAs should be session aware both for secured and unsecured session implementation.

2014-02-21 Thread Thejas M Nair (JIRA)

[ 
https://issues.apache.org/jira/browse/HIVE-6484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13909041#comment-13909041
 ] 

Thejas M Nair commented on HIVE-6484:
-

The FS instance leak described in HIVE-4501 can be fixed with this change.


 HiveServer2 doAs should be session aware both for secured and unsecured 
 session implementation.
 ---

 Key: HIVE-6484
 URL: https://issues.apache.org/jira/browse/HIVE-6484
 Project: Hive
  Issue Type: Improvement
  Components: HiveServer2
Affects Versions: 0.13.0
Reporter: Vaibhav Gumashta
Assignee: Vaibhav Gumashta
 Fix For: 0.13.0


 Currently in unsecured case, the doAs is performed by decorating 
 TProcessor.process method. This has been causing cleanup issues as we end up 
 creating a new clientUgi for each request rather than for each session. This 
 also cleans up the code.
 [~thejas] Probably you can add more if you've seen other issues related to 
 this.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)