You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Jonathan Hsieh (JIRA)" <ji...@apache.org> on 2012/06/03 02:38:23 UTC
[jira] [Updated] (HBASE-6155) [copytable] Unexpected behavior if
--starttime is not specifed but --endtime is.
[ https://issues.apache.org/jira/browse/HBASE-6155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Hsieh updated HBASE-6155:
----------------------------------
Labels: noob (was: )
> [copytable] Unexpected behavior if --starttime is not specifed but --endtime is.
> --------------------------------------------------------------------------------
>
> Key: HBASE-6155
> URL: https://issues.apache.org/jira/browse/HBASE-6155
> Project: HBase
> Issue Type: Improvement
> Affects Versions: 0.90.6, 0.92.1, 0.94.0, 0.96.0
> Reporter: Jonathan Hsieh
> Labels: noob
>
> If one uses copytable and specifies only an endtime, I'd expect to include all rows from unix epoch time upto the specified endtime. Instead, it copies all the rows.
> The workaround for copies with this kind of range is to specify --startime=1 (Note not --starttime=0), which is also unintuitive.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira