[
https://issues.apache.org/jira/browse/HBASE-15680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15259176#comment-15259176
]
Hudson commented on HBASE-15680:
--------------------------------
FAILURE: Integrated in HBase-Trunk_matrix #873 (See
[https://builds.apache.org/job/HBase-Trunk_matrix/873/])
HBASE-15680 Examples in shell help message for TIMERANGE scanner (stack: rev
e512c40ad58da28db42bb99de23d467d8db296cb)
* hbase-shell/src/main/ruby/shell/commands/scan.rb
* hbase-shell/src/main/ruby/shell/commands/set_visibility.rb
> Examples in shell help message for TIMERANGE scanner specifications should
> use milliseconds instead of seconds
> --------------------------------------------------------------------------------------------------------------
>
> Key: HBASE-15680
> URL: https://issues.apache.org/jira/browse/HBASE-15680
> Project: HBase
> Issue Type: Improvement
> Components: shell
> Reporter: Li Fanxi
> Priority: Trivial
> Labels: beginner
> Fix For: 2.0.0
>
> Attachments: HBASE-15680.patch
>
> Original Estimate: 5m
> Remaining Estimate: 5m
>
> {code}
> hbase> scan 't1', {COLUMNS => 'c1', TIMERANGE => [1303668804, 1303668904]}
> hbase> set_visibility 't1', '(A&B)|C', {COLUMNS => 'c1',
> TIMERANGE => [1303668804, 1303668904]}
> {code}
> Examples for 'scan' and 'set_visibility' command use 10-digit timestamp (in
> seconds) as the parameter for the TIMERANGE scanner specifications. However,
> TIMERANGE only accepts milliseconds as its parameters.
> To avoid misleading, suggest to improve the examples by using 13-digit
> timestamps (in milliseconds).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
