hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ramkrishna.s.vasudevan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-19092) Make Tag IA.LimitedPrivate and expose for CPs
Date Tue, 31 Oct 2017 04:57:00 GMT

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

ramkrishna.s.vasudevan commented on HBASE-19092:
------------------------------------------------

bq.At this stage I'd say just let them have ECB. Could even filter it via the CP Env to remove
the SequenceId method.... Or throw exception if they try to mess w/ it.
Ok. So i wont add any new builder and will leave ECB as private for now. Which means for CPs
we don't give them a chance to build  a tag. For now they can read the tags? Is that fine?
I think making ECB LimitedPrivate is not right IMHO. What do you think?

> Make Tag IA.LimitedPrivate and expose for CPs
> ---------------------------------------------
>
>                 Key: HBASE-19092
>                 URL: https://issues.apache.org/jira/browse/HBASE-19092
>             Project: HBase
>          Issue Type: Sub-task
>          Components: Coprocessors
>            Reporter: ramkrishna.s.vasudevan
>            Assignee: ramkrishna.s.vasudevan
>            Priority: Critical
>             Fix For: 2.0.0-alpha-4
>
>         Attachments: HBASE-19092-branch-2.patch, HBASE-19092_001-branch-2.patch
>
>
> We need to make tags as LimitedPrivate as some use cases are trying to use tags like
timeline server. The same topic was discussed in dev@ and also in HBASE-18995.
> Shall we target this for beta1 - cc [~saint.ack@gmail.com].
> So once we do this all related Util methods and APIs should also move to LimitedPrivate
Util classes.



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

Mime
View raw message