You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Huaxiang Sun (Jira)" <ji...@apache.org> on 2020/11/04 18:21:00 UTC

[jira] [Created] (HBASE-25247) Followup jira to encap all meta replica mode/selector processing into CatalogReplicaModeManager

Huaxiang Sun created HBASE-25247:
------------------------------------

             Summary: Followup jira to encap all meta replica mode/selector processing into CatalogReplicaModeManager
                 Key: HBASE-25247
                 URL: https://issues.apache.org/jira/browse/HBASE-25247
             Project: HBase
          Issue Type: Sub-task
          Components: meta
            Reporter: Huaxiang Sun
            Assignee: Huaxiang Sun


This is follow up with Stack's comments in [https://github.com/apache/hbase/pull/2584/commits/d99c2b0ccfd2a57150e984742d097d1e1fcc47b0.]

{quote}
h4. *[saintstack|https://github.com/saintstack]* [6 days ago|https://github.com/apache/hbase/pull/2584/commits/d99c2b0ccfd2a57150e984742d097d1e1fcc47b0#r514558880] 
Member
Yeah, said this before but in follow-on, would be good to shove all this stuff into a CatalogReplicaMode class. Internally this class would figure which policy to run. It would have a method that took a Scan that allowed decorating the Scan w/ whatever the mode needed to implement its policy. Later.
 
[!https://avatars1.githubusercontent.com/u/62515050?s=60&v=4|width=28,height=28!|https://github.com/huaxiangsun] 
h4. *[huaxiangsun|https://github.com/huaxiangsun]* [6 days ago|https://github.com/apache/hbase/pull/2584/commits/d99c2b0ccfd2a57150e984742d097d1e1fcc47b0#r514587250] 
Author Member
Now I thought about it, it makes sense. Maybe a CatalogReplicaModeManager class which encaps mode and selector?
Let me create a followup jira after this is merged.
 
{quote}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)