[
https://issues.apache.org/jira/browse/HBASE-9496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13765180#comment-13765180
]
Jonathan Hsieh edited comment on HBASE-9496 at 9/12/13 5:46 AM:
----------------------------------------------------------------
I'm actually for restoring the the old constructor but hiding the new one.
I came up with a case -- 3rd party coprocs like phoenix probably create Results
and populate them. This makes me think that we should hide the ctor and maybe
have a separate builder that is @InterfaceAudience.LimitedPrivate("coproc").
Or if we could just mark the ctor method with that visibility annotation...
was (Author: jmhsieh):
I'm actually for restoring the the old constructor but hiding the new one?
I came up with a case -- 3rd party coprocs like phoenix probably create Results
and populate them. This makes me think that we should hide the ctor and maybe
have a separate builder that is @InterfaceAudience.LimitedPrivate("coproc").
Or if we could just mark the ctor method with that visibility annotation...
> make sure HBase APIs are compatible between 0.94 and 0.96
> ---------------------------------------------------------
>
> Key: HBASE-9496
> URL: https://issues.apache.org/jira/browse/HBASE-9496
> Project: HBase
> Issue Type: Sub-task
> Reporter: Sergey Shelukhin
> Assignee: Sergey Shelukhin
> Priority: Blocker
> Fix For: 0.96.0
>
> Attachments: HBASE-9496-v0-96.patch
>
>
> Follow-up for HBASE-9477.
> Some other methods are now different between 94 and 96
> (Result::getColumnLatest, Put::get, anything that takes a collection of Cell,
> e.g. Result ctor, Mutation::setFamilyMap etc.).
> I am assuming things that accept Cell (Increment::add,
> Delete::addDeleteMarker) don't need to change.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
