Yes but its not a client-usable, stable API class. The NameNode too is
a service, not a directly user-usable object. The interface changes
from release to release, and methods may get added/deprecated/removed
without us considering the user impact cause it isn't meant to be a
user class.
For all f
Hi Harsh,
Why do you consider ClientProtocol to be an unsupported and non-public
class/interface? Isn't that what the concrete Namenode class is based
on?
Thanks.
On Wed, Feb 1, 2012 at 8:16 PM, Harsh J wrote:
> Michael,
>
> These are non-public, unsupported classes you are trying to use here
Michael,
These are non-public, unsupported classes you are trying to use here.
We'd not recommend doing that unless your goal was to experiment with
something at most.
But to technically answer your question, you can get over this if you
disable permissions itself on the HDFS level. Impersonating
Hi folks,
I'm trying to connect to a NameNode using Hadoop's RPC ClientProtocol
class. Code below:
InetSocketAddress address = new InetSocketAddress("namenode", 9000);
Configuration conf = new Configuration();
ClientProtocol client =
(ClientProtocol) RPC.waitForProxy(ClientProtocol.cla
