You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Lars Hofhansl (JIRA)" <ji...@apache.org> on 2014/12/10 06:04:14 UTC

[jira] [Commented] (HBASE-10071) Backport HBASE-6592 to 0.94 branch

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

Lars Hofhansl commented on HBASE-10071:
---------------------------------------

[~busbey]?

> Backport HBASE-6592 to 0.94 branch
> ----------------------------------
>
>                 Key: HBASE-10071
>                 URL: https://issues.apache.org/jira/browse/HBASE-10071
>             Project: HBase
>          Issue Type: Improvement
>          Components: shell
>    Affects Versions: 0.94.14
>            Reporter: cuijianwei
>            Assignee: Sean Busbey
>             Fix For: 0.94.26
>
>         Attachments: HBASE-10071-0.94-v1.patch
>
>
> Users tend to run hbase shell to query hbase quickly. The result will be shown as binary format which may not look clear enough when users write columns using specified types, such as long/int/short. Therefore, it may be helpful if the results could be shown as specified format. We make a patch to extend get/scan in hbase shell in which user could specify the data type in get/scan for each column as:
> {code}
> scan 'table', {COLUMNS=>['CF:QF:long']}
> get 'table', 'r0', {COLUMN=>'CF:QF:long'}
> {code}
> Then, the result will be shown as Long type. The result of above get will be:
> {code}
> COLUMN                                        CELL                                                                                                           
>  CF:QF                                timestamp=24311261, value=24311229
> {code}
> This extended format is compatible with previous format, if users do not specify the data type, the command will also work and output binary format.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)