You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Ramkumar Vadali (JIRA)" <ji...@apache.org> on 2012/08/07 00:29:02 UTC
[jira] [Created] (HBASE-6519) FSRegionScanner should be in its own
file
Ramkumar Vadali created HBASE-6519:
--------------------------------------
Summary: FSRegionScanner should be in its own file
Key: HBASE-6519
URL: https://issues.apache.org/jira/browse/HBASE-6519
Project: HBase
Issue Type: Improvement
Components: util
Environment: mac osx, jdk 1.6
Reporter: Ramkumar Vadali
Priority: Minor
I found this problem in the 0.89-fb branch.
I was not able to start the master because of a ClassNotFoundException for FSRegionScanner.
FSRegionScanner is a top-level class in FSUtils.java. Moving it to a separate file solved the problem.
--
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
[jira] [Commented] (HBASE-6519) FSRegionScanner should be in its
own file
Posted by "Ramkumar Vadali (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13429580#comment-13429580 ]
Ramkumar Vadali commented on HBASE-6519:
----------------------------------------
https://reviews.facebook.net/D4533
> FSRegionScanner should be in its own file
> -----------------------------------------
>
> Key: HBASE-6519
> URL: https://issues.apache.org/jira/browse/HBASE-6519
> Project: HBase
> Issue Type: Improvement
> Components: util
> Environment: mac osx, jdk 1.6
> Reporter: Ramkumar Vadali
> Priority: Minor
>
> I found this problem in the 0.89-fb branch.
> I was not able to start the master because of a ClassNotFoundException for FSRegionScanner.
> FSRegionScanner is a top-level class in FSUtils.java. Moving it to a separate file solved the problem.
--
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