hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-18067) Support a default converter for data read shell commands
Date Fri, 19 May 2017 16:50:04 GMT

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

Josh Elser updated HBASE-18067:
    Attachment: HBASE-18067.002.patch

.002 Fix some minor things I noticed transcribing the patch (nothing functionally different,
just consistent).

> Support a default converter for data read shell commands
> --------------------------------------------------------
>                 Key: HBASE-18067
>                 URL: https://issues.apache.org/jira/browse/HBASE-18067
>             Project: HBase
>          Issue Type: Improvement
>          Components: shell
>            Reporter: Josh Elser
>            Assignee: Josh Elser
>            Priority: Minor
>             Fix For: 2.0.0
>         Attachments: HBASE-18067.001.patch, HBASE-18067.002.patch
> The {{get}} and {{scan}} shell commands have the ability to specify some complicated
syntax on how to encode the bytes read from HBase on a per-column basis. By default, bytes
falling outside of a limited range of ASCII are just printed as hex.
> It seems like the intent of these converts was to support conversion of certain numeric
columns as a readable string (e.g. 1234).
> However, if non-ascii encoded bytes are stored in the table (e.g. UTF-8 encoded bytes),
we may want to treat all data we read as UTF-8 instead (e.g. if row+column+value are in Chinese).
It would be onerous to require users to enumerate every column they're reading to parse as
UTF-8 instead of the limited ascii range. We can provide an option to encode all values retrieved
by the command.

This message was sent by Atlassian JIRA

View raw message