[
https://issues.apache.org/jira/browse/HBASE-15816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16069249#comment-16069249
]
Andrew Purtell commented on HBASE-15816:
----------------------------------------
This patch makes changes to Public/Stable interfaces. They are method additions
so would be binary compatible with older versions but client code that uses
them would not be compatible with older releases. HBase compatibility
guidelines allow this no problem for master, branch-2, and branch-1. I believe
it is also allowed for branch-1.3 and branch-1.2 but would like to hear from
[~mantonov] and [~busbey] . See PHOENIX-3983 for latest rationale. It would be
much easier for Phoenix to pass priority through in RPCs than reverse engineer
the client intention on the server side. They'd need support in releasing
versions.
> 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.patch, HBASE-15816-v1.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.4.14#64029)
