You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Andrew Purtell (JIRA)" <ji...@apache.org> on 2019/02/01 20:32:02 UTC

[jira] [Updated] (HBASE-20884) Replace usage of our Base64 implementation with java.util.Base64

     [ https://issues.apache.org/jira/browse/HBASE-20884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrew Purtell updated HBASE-20884:
-----------------------------------
    Fix Version/s:     (was: 1.5.0)

> 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, 1.3.3, 1.4.6, 1.2.7, 2.1.1, 2.0.2
>
>         Attachments: HBASE-20884.branch-1.001.patch, HBASE-20884.branch-1.002.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)