[ https://issues.apache.org/jira/browse/HBASE-8199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13615228#comment-13615228 ]
Hudson commented on HBASE-8199: ------------------------------- Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #466 (See [https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/466/]) HBASE-8199 Eliminate exception for ExportSnapshot against the null table snapshot (Julian Zhou) (Revision 1461340) Result = FAILURE mbertozzi : Files : * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/snapshot/ExportSnapshot.java * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/snapshot/TestExportSnapshot.java > 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: Improvement > Components: snapshots > Affects Versions: 0.95.0, 0.94.6, 0.94.7 > Reporter: Julian Zhou > Assignee: Julian Zhou > Priority: Minor > Fix For: 0.95.0, 0.94.7 > > Attachments: HBASE-8199-0.94.patch, HBASE-8199-trunk.patch, > HBASE-8199-with-test.patch > > > In the test environment, when snapshoting the null table (with no data), > snapshot artifact can be generated successfully with 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