[
https://issues.apache.org/jira/browse/HBASE-19746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16447285#comment-16447285
]
Chia-Ping Tsai commented on HBASE-19746:
----------------------------------------
{quote}I do not understand your comments about API compatibility. What exactly
do you mean here?
{quote}
You can compile your code without any changing after updating the hbase version
from 1.x to 2.0. It means you can change the version of hbase dependencies and
then still succeed to build the project.
{quote}It's a major version so we are allowed to break API. We do this either
in 2.0 by _not_ adding a default or in 3.0 by adding the _default_ method and
removing it later. So for me that's not an argument.
{quote}
Pardon me. I just catch your point. :( So you prefer to remove the default
impl (The API is break here) to enforce user to implement the #getType in 2.0
rather than delaying the break to 3.0? If so, I'm fine to revert this patch.
{quote}It's getting late here so I'll wait until the US wakes up on Monday and
will see if anyone else has an opinion. If no one jumps in I'll ping the dev
list.
{quote}
:)
> Add default impl to Cell#getType
> --------------------------------
>
> Key: HBASE-19746
> URL: https://issues.apache.org/jira/browse/HBASE-19746
> Project: HBase
> Issue Type: Sub-task
> Reporter: Chia-Ping Tsai
> Assignee: Chia-Ping Tsai
> Priority: Critical
> Fix For: 2.0.0
>
> Attachments: HBASE-19746.v0.patch, HBASE-19746.v1.patch,
> HBASE-19746.v1.qa.patch
>
>
> Noticed this issue when migrating the app to branch-2.
> {{Cell}} is IA.Public so it should obey our compatibility rules. Not sure
> whether any related discussion had be in HBASE-19112. It worthwhile, however,
> to raise this issue again.
> FYI [~anoopsamjohn] [~ram_krish] [~stack]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
