hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Enis Soztutar (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-6834) HBaseClusterManager shell code breaks hadoop-2.0 build
Date Wed, 19 Sep 2012 02:18:07 GMT

    [ https://issues.apache.org/jira/browse/HBASE-6834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13458357#comment-13458357

Enis Soztutar commented on HBASE-6834:

Shell and ShellCommandExecutor are non-trivial classes. I am not sure we should just copy
them. If we run into this kind of problems in the future, we might develop our own, or maybe
use the shims layer. wdyt? 
> HBaseClusterManager shell code breaks hadoop-2.0 build
> ------------------------------------------------------
>                 Key: HBASE-6834
>                 URL: https://issues.apache.org/jira/browse/HBASE-6834
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Gregory Chanan
>            Assignee: Enis Soztutar
> I get the following error:
> {noformat}
> HBaseClusterManager.java:[73,23] getExecString() in org.apache.hadoop.hbase.HBaseClusterManager.RemoteShell
cannot override getExecString() in org.apache.hadoop.util.Shell.ShellCommandExecutor; attempting
to assign weaker access privileges; was public
> {noformat}
> the issue is that getExecString() is declared public in hadoop-2.0, but protected in
hadoop-1.0.  In HBase, it is declared protected, and you can't downgrade from public to protected.
> We can just declare the function public and that seems to work, but given that in hadoop
the class is declared
> {code}
> @InterfaceAudience.LimitedPrivate({"HDFS", "MapReduce"})
> {code}
> perhaps we should just copy the class into hbase source.

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

View raw message