[
https://issues.apache.org/jira/browse/HBASE-19897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16345710#comment-16345710
]
Chia-Ping Tsai commented on HBASE-19897:
----------------------------------------
bq. This is a breaking API change?
IIRC, we require user to recompile their code if they want to migrate code to
2.0. This patch changes the return type from void to RowMutations. User wont
assign the void to any object I believe. The concern here is that users have
their custom RowMutations...Yep, we should add the new methods to avoid the
possible API breaking.
> RowMutations should follow the fluent pattern
> ---------------------------------------------
>
> Key: HBASE-19897
> URL: https://issues.apache.org/jira/browse/HBASE-19897
> Project: HBase
> Issue Type: New Feature
> Reporter: Chia-Ping Tsai
> Assignee: Chia-Ping Tsai
> Priority: Minor
> Fix For: 2.0.0-beta-2
>
> Attachments: HBASE-19897.v0.patch
>
>
> Other row ops, including {{Put}}, {{Delete}}, {{Get}}, {{Scan}}, do have the
> fluent interface. Also, Changing the return type from {{Void}} to
> {{RowMutations}} won't break the API BC (unless someone has interest in
> {{Void}} object...)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
