[
https://issues.apache.org/jira/browse/HBASE-17762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15903767#comment-15903767
]
Esteban Gutierrez edited comment on HBASE-17762 at 3/9/17 8:13 PM:
-------------------------------------------------------------------
Also, looks like the change is only affecting client side logging and I think
we should have this in the server side too. One thing I've been considering too
is that we should add an optional string to VersionInfo to provide additional
information to identify the client (think of something similar to use
mapreduce.task.attempt.id to identify the clients in HDFS). If that sounds
interesting for you guys I'd be happy to work in a patch for that.
was (Author: esteban):
Also, looks like the change is only affecting client side logging and I think
we should have this in the server side too. One thing I've been considering too
is that we should add an optional string to VersionInfo two provide additional
information to identify the client (think of something similar to use
mapreduce.task.attempt.id to identify the clients in HDFS). If that sounds
interesting for you guys I'd be happy to work in a patch for that.
> Add logging to HBaseAdmin for user initiated tasks
> --------------------------------------------------
>
> Key: HBASE-17762
> URL: https://issues.apache.org/jira/browse/HBASE-17762
> Project: HBase
> Issue Type: Task
> Reporter: churro morales
> Assignee: churro morales
> Fix For: 2.0.0, 1.4.0, 0.98.25
>
> Attachments: HBASE-17762.patch, HBASE-17762.v1.patch
>
>
> Things like auditing a forced major compaction are really useful and right
> now there is no logging when this is triggered. Other actions may require
> logging as well.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
