You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "bbeaudreault (via GitHub)" <gi...@apache.org> on 2023/06/23 18:19:47 UTC

[GitHub] [hbase] bbeaudreault commented on pull request #5306: HBASE-27657: Connection and Request Attributes

bbeaudreault commented on PR #5306:
URL: https://github.com/apache/hbase/pull/5306#issuecomment-1604672536

   Since `RpcCall` interface is LimitedPrivate with exposure to COPROC, one could decide to inspect Connection or Request attributes in their coprocessor. For example, `RpcServer.getCurrentCall().get().getConnectionHeader().getAttributes()` (or `getHeader().getAttributes()` for Request attributes).
   
   These could be used in various ways in coprocessors depending on the implementation. They also exist as a building block for other native features in the future, like Quota Groups that Ray mentioned. We also plan to expose them in SlowLog payload, so one could get valuable tracing information from their clients.
   
   Sounds like Duo did not have an issue with the API defined here, so we could just encode this into a simple design doc with slightly more formal version of the above to describe how they could be used and why they are an improvement over Operation attributes.


-- 
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-unsubscribe@hbase.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org