rmdmattingly opened a new pull request, #5326: URL: https://github.com/apache/hbase/pull/5326
[Here's an initial design doc](https://docs.google.com/document/d/1cGEmUn2kAPhn_Q18DvAOhigtCbnQ8ia6oV4OvMb5DyU/edit?usp=sharing) I'm hoping to get feedback on the design proposed above. Currently we have the ability to set Operation attributes, via Get.setAttribute, etc. It would be useful to be able to set attributes at the request and connection level. These levels can result in less duplication. For example, send some attributes once per connection instead of for every one of the millions of requests a connection might send. Or send once for the request, instead of duplicating on every operation in a multi request. Additionally, the Connection and RequestHeader are more globally available on the server side. Both can be accessed via RpcServer.getCurrentCall(), which is useful in various integration points – coprocessors, custom queues, quotas, slow log, etc. Operation attributes are harder to access because you need to parse the raw Message into the appropriate type to get access to the getter. This PR introduces two new avenues for providing attributes: * passing in a map of connection attributes to `ConnectionFactory#createConnection` * passing in a map of request attributes to `TableBuilder#setRequestAttributes` We've also added end-to-end tests for both systems. cc @bbeaudreault @hgromer @saijmo @eab148 @bozzkar -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@hbase.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
