You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Julian Zhou (JIRA)" <ji...@apache.org> on 2013/03/26 16:31:16 UTC

[jira] [Updated] (HBASE-8199) Eliminate exception for ExportSnapshot against the null table snapshot (with no data in)

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

Julian Zhou updated HBASE-8199:
-------------------------------

    Status: Patch Available  (was: Open)
    
> Eliminate exception for ExportSnapshot against the null table snapshot (with no data in)
> ----------------------------------------------------------------------------------------
>
>                 Key: HBASE-8199
>                 URL: https://issues.apache.org/jira/browse/HBASE-8199
>             Project: HBase
>          Issue Type: Bug
>          Components: snapshots
>    Affects Versions: 0.94.6, 0.95.0, 0.94.7
>            Reporter: Julian Zhou
>            Assignee: Julian Zhou
>            Priority: Minor
>             Fix For: 0.95.0, 0.94.6
>
>
> In the test environment, when snapshoting the null table (with no data), snapshot artifact can be generated successfully which snapshot meta data, while there is no CF data under region dir. Then when exporting this null snapshot via ExportSnapshot, "java.io.IOException: No input paths specified in job" occurred, which affects the normal application flow. 
> But seems snapshot for null table also makes sense just with the meta information (.snapshot/), although ".archive/" does not show up. Later snapshot restore seems work from this "dummy" snapshot artifact with no CF data.
> Just eliminate exception for ExportSnapshot against the null table snapshot to make application work through.

--
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