[
https://issues.apache.org/jira/browse/HBASE-7623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13557477#comment-13557477
]
Jimmy Xiang commented on HBASE-7623:
------------------------------------
That's a good point. The issue is that we have some problem to get the user if
the client runs on some windows platform as a system user. However, the
security is not needed, so we don't need the username.
As to the RPC connection setup, we are going to find out. I assume we don't
need a username either since security is not a concern here. On the server
side, do we mandate a username in accepting a RPC connection?
> Username is not available for HConnectionManager to use in HConnectionKey
> -------------------------------------------------------------------------
>
> Key: HBASE-7623
> URL: https://issues.apache.org/jira/browse/HBASE-7623
> Project: HBase
> Issue Type: Improvement
> Components: Client
> Reporter: Jimmy Xiang
> Assignee: Jimmy Xiang
> Priority: Minor
> Attachments: trunk-7623.patch
>
>
> Sometimes, some non-IOException prevents User.getCurrent() to get a username.
> It makes it impossible to create a HConnection. We should catch all
> exception here:
> {noformat}
> try {
> User currentUser = User.getCurrent();
> if (currentUser != null) {
> username = currentUser.getName();
> }
> } catch (IOException ioe) {
> LOG.warn("Error obtaining current user, skipping username in
> HConnectionKey",
> ioe);
> }
> {noformat}
> Not just IOException, so that client can move forward.
--
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
