[
https://issues.apache.org/jira/browse/HBASE-13358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14524509#comment-14524509
]
Srikanth Srungarapu commented on HBASE-13358:
---------------------------------------------
bq. Actually a public API, when removing or changing, we have to deprecate it
for a full major version.. Here we deprecate it in btw 1.x release lines.. It
will be correct to deprecate in 2.0 also and remove in 3.0
Is this policy is ref guide? I missed this. Sorry for that.
bq. IMO , better we stick with our deprecation rule
Sure. I pushed two addendums here. So reverting all of them would look a bit
awkward. Instead, I would prefer opening a sub-task to bring them back. Would
that be okay?
> Upgrade VisibilityClient API to accept Connection object.
> ---------------------------------------------------------
>
> Key: HBASE-13358
> URL: https://issues.apache.org/jira/browse/HBASE-13358
> Project: HBase
> Issue Type: Improvement
> Reporter: Srikanth Srungarapu
> Assignee: Matt Warhaftig
> Priority: Minor
> Fix For: 2.0.0, 1.2.0
>
> Attachments: 13358-addendum.txt, 13358-addendum.txt,
> HBASE-13358-1.2_v5.patch, HBASE-13358-master_v5.patch, HBASE-13358.patch,
> HBASE-13358_v2.patch, HBASE-13358_v3.patch, HBASE-13358_v4.patch
>
>
> From VisibilityClient class:
> {code}
> // TODO: Make it so caller passes in a Connection rather than have us do
> this expensive
> // setup each time. This class only used in test and shell at moment
> though.
> {code}
> Basically, this is the VC's counterpart of HBASE-13171.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
