[
https://issues.apache.org/jira/browse/HBASE-6699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13445721#comment-13445721
]
Himanshu Vashishtha commented on HBASE-6699:
--------------------------------------------
re: PSEUDO_METHOD_NAME_TO_SET_USER: We do have other references to HConstants
though? For Cluster_ID?
re: indent: okay.
re: Config param: I am +0 on that. Will do.
re: Comments: As I was reading the related code, i tried to use /**/ for multi
line comments.
bq. LOG.error("Got exception while processing call with Id: " +id, e);
No, we just closed the connection if in this code path. This error is just to
print which call made it so.
re: HBaseServer: So, the username is set in RequestContext. Now, any code which
wants to log can call this and get the username. For example, one can use
AcessController (while using as a normal coprocessor).
> 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
