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

Anoop Sam John commented on HBASE-19092:
----------------------------------------

bq. we want Tags integral to Cell, not apart as they have been, so getting Tags 
from Cell/ExtendedCell is where we want to be
Exactly. This is what I too considered.  We want Tags to be part of Cell. When 
we do it for say 3.0, we need getTags in Cell. Not in ExtendedCell.  We have to 
expose tags to client side also.  So if we add to ExtendedCell today, it is 
bound to change again tomorrow right? To be to Cell.  That is what my 
consideration was.  Then having in a static util API way is not that bad as 
type casting calls on ExtendedCell.  In 3.0, we would deprecate that static 
against Cell#getTags().   Any way take a call... Am ok for any thing decided 
here.

> 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 [~saint....@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)

Reply via email to