[
https://issues.apache.org/jira/browse/HBASE-19897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16349283#comment-16349283
]
Chia-Ping Tsai commented on HBASE-19897:
----------------------------------------
{quote}because the new add has a different return, the compiler is fine w/ this
'override' it seems.
{quote}
It is not related to return type. Compiler always can choose the correct method
according to the passed type. After applying this patch, the *rm.add(new Put)*
still call the deprecated *rm#add(Put)*. If users want to try the fluent way,
they must to write *rm.add((Mutation) new Put).*
> 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, HBASE-19897.v1.patch,
> HBASE-19897.v1.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)
