phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vincent Poon (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PHOENIX-3983) Index rebuild scans should not be using the ServerRpcControllerFactory
Date Fri, 30 Jun 2017 20:51:00 GMT

    [ https://issues.apache.org/jira/browse/PHOENIX-3983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16070701#comment-16070701
] 

Vincent Poon commented on PHOENIX-3983:
---------------------------------------

HBASE-15816 requires us to set the priority on each Operation.  One way to maintain backwards
compatibility would be to use reflection to dynamically check if the method setPriority exists
on Operation.  Another way would be to have some interface, call it PrioritySetter, which
we then call for each operation.  Then depending on the HBase version we inject either a DummyPrioritySetter
or an actual PrioritySetter which calls setPriority on the Operation.

Cleanest way code-wise would be to just have another branch.  We could then get rid of the
existing priority setting stuff and just add the new calls to Operation#setPriority.

> Index rebuild scans should not be using the ServerRpcControllerFactory
> ----------------------------------------------------------------------
>
>                 Key: PHOENIX-3983
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-3983
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: Samarth Jain
>            Assignee: Samarth Jain
>         Attachments: PHOENIX-3983.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message