[
https://issues.apache.org/jira/browse/HBASE-5609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Drzal updated HBASE-5609:
---------------------------------
Release Note: Added the ability to add identifiers to client operations.
These identifiers will be output with slow query logging. The could be used to
identify the piece of code that initiated the operation. This could be
anything from a module name to a class.method with a line number.
Status: Patch Available (was: Open)
> 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
> Attachments: HBASE-5609-v2.patch, HBASE-5609-v3.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
