[
https://issues.apache.org/jira/browse/HBASE-20884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Drob updated HBASE-20884:
------------------------------
Hadoop Flags: Incompatible change,Reviewed
Release Note:
Class org.apache.hadoop.hbase.util.Base64 has been removed in it's entirety
from HBase 2+. In HBase 1, unused methods have been removed from the class and
the audience was changed from Public to Private. This class was originally
intended as an internal utility class since inception, and should not have been
advertised as public to end-users.
This represents an incompatible change for users who relied on this
implementation. An alternative implementation for affected clients is available
at java.util.Base64 when using Java 8 or newer. For clients seeking to restore
this specific implementation, it is available in the public domain for download
at http://iharder.sourceforge.net/current/java/base64/
> Replace usage of our Base64 implementation with java.util.Base64
> ----------------------------------------------------------------
>
> Key: HBASE-20884
> URL: https://issues.apache.org/jira/browse/HBASE-20884
> Project: HBase
> Issue Type: Task
> Reporter: Mike Drob
> Assignee: Mike Drob
> Priority: Major
> Fix For: 3.0.0
>
> Attachments: HBASE-20884.branch-1.001.patch,
> HBASE-20884.master.001.patch
>
>
> We have a public domain implementation of Base64 that is copied into our code
> base and infrequently receives updates. We should replace usage of that with
> the new Java 8 java.util.Base64 where possible.
> For the migration, I propose a phased approach.
> * Deprecate on 1.x and 2.x to signal to users that this is going away.
> * Replace usages on branch-2 and master with j.u.Base64
> * Delete our implementation of Base64 on master.
> Does this seem in line with our API compatibility requirements?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
