hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Appy (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-19092) Make Tag IA.LimitedPrivate and expose for CPs
Date Thu, 26 Oct 2017 20:23:00 GMT

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

Appy commented on HBASE-19092:
------------------------------

Yes, only the interface please.

And these utils & their scope! The way we are heading, looks like we'll have a big mess
with naming utils.
We now have CellUtil (public), InternalCellUtil(private) and then there will be <Some>CellUtil
(LP)
But for TagUtil, the names are: TagUtil (being made LP), and if decide to do its cleanup in
future or make things public, .....PublicTagUtil/PrivateTagUtil?(sigh)
Can we please decide the names for utils and use them consistently, that is to say, rename
TagUtil to be consistent with what we'll name IA.LP <Some>CellUtil.

> 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
>
>
> 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