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

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

The main discussion with Anoop was that if to really add the new Tag APIs in 
ExtendedCell (though we make it LP).
So he was of the opinion that since CPs are not using ExtendedCell if we add 
these APIs in ExtendedCell it would mean that we need to do a typecast and that 
is not straightforward. 
Instead have some static methods only. So shall we add getTags(Cell) to the Tag 
interface only? Currently Tag is only for specific Tags but lets change it now?
If not the other options is introduce 'Tags' (note the 's') interface and add 
getTags(Cell) to that interface and also have 'Tag' interface.
Thoughts/suggstion? [[email protected]] and [~chia7712].


> 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-beta-1
>
>         Attachments: HBASE-19092-branch-2.patch, 
> HBASE-19092-branch-2_5.patch, HBASE-19092-branch-2_5.patch, 
> HBASE-19092.branch-2.0.02.patch, HBASE-19092_001-branch-2.patch, 
> HBASE-19092_001.patch, HBASE-19092_002-branch-2.patch, HBASE-19092_002.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 [[email protected]].
> 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)

Reply via email to