[ 
https://issues.apache.org/jira/browse/HBASE-5609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13289798#comment-13289798
 ] 

Hudson commented on HBASE-5609:
-------------------------------

Integrated in HBase-0.94-security #35 (See 
[https://builds.apache.org/job/HBase-0.94-security/35/])
    HBASE-5609 Add the ability to pass additional information for slow query 
logging (Revision 1346509)

     Result = SUCCESS
stack : 
Files : 
* /hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/client/Get.java
* 
/hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/client/Mutation.java
* 
/hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/client/OperationWithAttributes.java
* /hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/client/Scan.java
* 
/hbase/branches/0.94/src/test/java/org/apache/hadoop/hbase/client/TestAttributes.java

                
> Add the ability to pass additional information for slow query logging
> ---------------------------------------------------------------------
>
>                 Key: HBASE-5609
>                 URL: https://issues.apache.org/jira/browse/HBASE-5609
>             Project: HBase
>          Issue Type: New Feature
>          Components: client, ipc
>            Reporter: Michael Drzal
>            Assignee: Michael Drzal
>            Priority: Minor
>             Fix For: 0.94.1
>
>         Attachments: HBASE-5609-v2.patch, HBASE-5609-v3.patch, 
> HBASE-5609-v4-094.txt, HBASE-5609-v4.patch, HBASE-5609.patch
>
>
> HBase-4117 added the ability to log information about queries that returned 
> too much data or ran for too long.  There is some information written as a 
> fingerprint that can be used to tell what table/column families/... are 
> affected.  I would like to extend this functionality to allow the client to 
> insert an identifier into the operation that gets output in the log.  The 
> idea behind this would be that if there were N places in the client 
> application that touched a given table in a certain way, you could quickly 
> narrow things down by inserting a className:functionName or similar 
> identifier.  I'm fully willing to go back on this if people think that it 
> isn't a problem in real life and it would just add complexity to the code.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to