The original plan was to get rid of the deprecated APIs as the first change
for the 5.x branch (before the branches diverged). Then it would have
applied to all the 4.x-1.* branches. Unfortunately that ship has sailed.
Probably easiest now to remove the deprecated API usage in 1.3 or master
branch and apply it to other branches (except 0.98). The 4.x-1.* branches
are all very similar.

We tried nuking the other branches, but we got community push back and
volunteers stepped up to become release managers. On the plus side, this
has worked out really well for 4.x-1.2 as now we have CDH support.

I think we should do a 4.14 release across all of our 4.x branches and then
start the conversation again about deprecating the 1.1 branch. I'd love to
do the same for 0.98, but it seems to be hanging around a bit longer than

On Fri, Apr 13, 2018 at 12:09 PM, Josh Elser <> wrote:

> It's definitely a goal, but I don't know of anyone actively working on
> that.
> What ever came about dropping old versions of HBase support? I thought we
> nuked <=1.2 (leaving just 1.3 and 1.4), but it seems like they have come
> back... The reason I ask: backporting the deprecation changes will be
> tough, and likely be tough for each branch they're targeted on. Trying to
> reduce where they need to go would be a big help.
> On 4/13/18 12:29 AM, James Taylor wrote:
>> Is it still the plan to get rid of deprecated HBase APIs in the 4.x
>> branches? This would ease the pain of porting changes between 4.x and 5.x
>> branches. I think it's likely that both branches will need to be
>> maintained
>> for some time. We'd likely need to get a Tephra release with this done
>> too,
>> but I think the work has already been done, no?
>> Thanks,
>> James

Reply via email to