[ https://issues.apache.org/jira/browse/HBASE-6699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13446108#comment-13446108 ]
Himanshu Vashishtha commented on HBASE-6699: -------------------------------------------- yes, the username is tied to the Connection. There is one extra rpc, to set/tie the username to the Connection, and is issued after sending the ConnectionHeader. It will be send one time whenever a connection is created (I will make it optional though, as Stack said). Its a non-blocking call to the server. With the first approach I mentioned, we could have set it in the ConnectionHeader itself and avoided any extra rpc, but it will be a change in a Writable. > Setting username in Connection in non-secure HBase > -------------------------------------------------- > > Key: HBASE-6699 > URL: https://issues.apache.org/jira/browse/HBASE-6699 > Project: HBase > Issue Type: Improvement > Components: ipc > Affects Versions: 0.92.0, 0.92.1, 0.94.0, 0.94.1 > Reporter: Himanshu Vashishtha > Assignee: Himanshu Vashishtha > Fix For: 0.92.3, 0.94.2 > > Attachments: HBase-6699-v1.patch > > > We recently had a requirement where we need to log the information about > various users who were using non-secure HBase cluster. > The user level logging is supported as part of security, but in 0.92, 0.94 > security related code is separate. This jira is about adding that support in > non-secure code. > This feature is already there in trunk, after we merge the security related > code. -- 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