hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ted Yu (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (HBASE-6155) [copytable] Unexpected behavior if --starttime is not specifed but --endtime is.
Date Wed, 19 Dec 2012 00:36:15 GMT

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

Ted Yu reassigned HBASE-6155:
-----------------------------

    Assignee: Prasanna
    
> [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
>            Assignee: Prasanna
>              Labels: noob
>         Attachments: 6155.diff
>
>
> 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
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message