You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Chia-Ping Tsai (JIRA)" <ji...@apache.org> on 2018/01/02 21:09:00 UTC

[jira] [Updated] (HBASE-19667) Get rid of MasterEnvironment#supportGroupCPs

     [ https://issues.apache.org/jira/browse/HBASE-19667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chia-Ping Tsai updated HBASE-19667:
-----------------------------------
      Resolution: Fixed
    Hadoop Flags: Reviewed
          Status: Resolved  (was: Patch Available)

Thanks for your reviews. [~appy]

> Get rid of MasterEnvironment#supportGroupCPs
> --------------------------------------------
>
>                 Key: HBASE-19667
>                 URL: https://issues.apache.org/jira/browse/HBASE-19667
>             Project: HBase
>          Issue Type: Sub-task
>          Components: Coprocessors
>            Reporter: Chia-Ping Tsai
>            Assignee: Chia-Ping Tsai
>             Fix For: 2.0.0-beta-2
>
>         Attachments: HBASE-19667.v0.patch
>
>
> copy the discussion from HBASE-19500.
> {quote}
> Appy:
> Can we remove {{if(((MasterEnvironment)getEnvironment()).supportGroupCPs) }} in so many places since CP in 2.0 are already broken left and right (and we'll have to solve legacy issue more holistically) What say Anoop Sam John?
> Chia:
> The cp user must do something to migrate their cp code from 1.x to 2.0 anyway, hence the check is unnecessary in 2.0 I'd say. Seems it is unrelated to this jira. Iron out it in another jira?
> Appy:
> Chia-Ping Tsai you can take up the check removal?
> {quote}



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