You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Roland Huss (JIRA)" <ji...@apache.org> on 2018/03/07 11:52:00 UTC

[jira] [Commented] (HBASE-272) [hbase] Add new Base64 dialects

    [ https://issues.apache.org/jira/browse/HBASE-272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16389447#comment-16389447 ] 

Roland Huss commented on HBASE-272:
-----------------------------------

[~jimk] sorry, for hijacking this issue (couldn't find a better anchor), but I'm looking for more information and history of the Base64.ORDERED algorithm. The original link to [http://www.faqs.org/qa/rfcc-1940.html] is unfortunately dead and I can't find anything about how this encoding is implemented (except the source of course, which is however quite hard to understand for me). 

 

Do you have any pointers for me (or maybe some history what happens to the spec ?)

 

thanks ...

... roland

> [hbase] Add new Base64 dialects
> -------------------------------
>
>                 Key: HBASE-272
>                 URL: https://issues.apache.org/jira/browse/HBASE-272
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Jim Kellerman
>            Priority: Major
>         Attachments: patch.txt
>
>
> Add new Base64 dialects:
> - Using Base64.URL_SAFE generates URL and file name friendly format as described in Section 4 of RFC3548. http://www.faqs.org/rfcs/rfc3548.html
> - Using Base64.ORDERED generates URL and file name friendly format  that preserves lexical ordering as described in  http://www.faqs.org/qa/rfcc-1940.html
> - The default is RFC3548 format



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)