[
https://issues.apache.org/jira/browse/HBASE-15816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15334470#comment-15334470
]
churro morales commented on HBASE-15816:
----------------------------------------
[~apurtell] yes i am still interested in carrying it forward.
The patch for removing annotation driven priorities became quite large as I had
to add that info to each protobuf message thus adding an optional priority
field to each of those. That got to be a huge patch and thought I would gauge
interest in this first patch before I finished the other patch. I can submit
another patch along with this patch, or throw it up on the review board if that
makes it easier for you guys.
I will add tests to confirm that the that the QOS != Normal for those annotated
methods keeps the same behavior.
Thanks for taking a look and I assume there is some interest and that I should
go ahead with the other patch for annotation driven priority removal.
> Provide client with ability to set priority on Operations
> ----------------------------------------------------------
>
> Key: HBASE-15816
> URL: https://issues.apache.org/jira/browse/HBASE-15816
> Project: HBase
> Issue Type: Improvement
> Affects Versions: 2.0.0
> Reporter: churro morales
> Assignee: churro morales
> Attachments: HBASE-15816-v1.patch, HBASE-15816.patch
>
>
> First round will just be to expose the ability to set priorities for client
> operations. For more background:
> http://mail-archives.apache.org/mod_mbox/hbase-dev/201604.mbox/%3CCA+RK=_BG_o=q8HMptcP2WauAinmEsL+15f3YEJuz=qbpcya...@mail.gmail.com%3E
> Next step would be to remove AnnotationReadingPriorityFunction and have the
> client send priorities explicitly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
