[
https://issues.apache.org/jira/browse/HBASE-18995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16221715#comment-16221715
]
ramkrishna.s.vasudevan commented on HBASE-18995:
------------------------------------------------
bq.Also, let's commit this to both master and branch-2? Reason being, removing
all this stuff now will make backports hard. Let's remove them after 2.0
release.
We may need another Util class just for CP and that is where the Tag related
things may come in.
So I think it is better we push this in first as is and then work on that other
tasks to create CPCellUtil. And regarding the commit I think we will commit now
to branch-2 and master as is and later work on removing the deprecated methods.
File a blocker against 3.0 and work with that JIRA?
> Move methods that are for internal usage from CellUtil to Private util class
> ----------------------------------------------------------------------------
>
> Key: HBASE-18995
> URL: https://issues.apache.org/jira/browse/HBASE-18995
> Project: HBase
> Issue Type: Sub-task
> Affects Versions: 2.0.0-alpha-3
> Reporter: ramkrishna.s.vasudevan
> Assignee: ramkrishna.s.vasudevan
> Priority: Critical
> Fix For: 2.0.0-alpha-4
>
> Attachments: HBASE-18995-branch-2.patch,
> HBASE-18995-branch-2_1.patch, HBASE-18995-branch-2_1.patch,
> HBASE-18995-branch-2_1.patch, HBASE-18995-branch-2_1.patch
>
>
> This was brought up long time back. We need to move some of the public APIs
> from CellUtil to internal private Util class because they are used in some
> internal flow and does not make sense to have it in a @public exposed Util
> class.
> The topic again came in HBASE-18945 RB comments also.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
