[
https://issues.apache.org/jira/browse/HBASE-18067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16020870#comment-16020870
]
Hudson commented on HBASE-18067:
--------------------------------
FAILURE: Integrated in Jenkins build HBase-HBASE-14614 #244 (See
[https://builds.apache.org/job/HBase-HBASE-14614/244/])
HBASE-18067 Allow default FORMATTER for shell put/get commands (elserj: rev
f1544c34669a69cb3ed163e45274f2fcca18e3eb)
* (edit) hbase-shell/src/main/ruby/shell/commands/scan.rb
* (edit) hbase-shell/src/main/ruby/shell/commands/get.rb
* (edit) hbase-shell/src/main/ruby/hbase/table.rb
* (edit) hbase-shell/src/main/ruby/hbase_constants.rb
* (add) hbase-shell/src/test/ruby/shell/converter_test.rb
> 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,
> HBASE-18067.003.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
(v6.3.15#6346)
