[
https://issues.apache.org/jira/browse/HBASE-15816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15347135#comment-15347135
]
Enis Soztutar commented on HBASE-15816:
---------------------------------------
What do you guys think about doing priorities at the HTD layer, rather than
per-request: HBASE-16095. It will be a maintenance issue where in every use,
the application has to make sure to set the priority correctly. It seems very
fragile to keep the framework level code (like Phoenix) to ensure to set
priorities in all cases.
> 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)
