Mailing-List: contact user-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@hadoop.apache.org
Received-SPF: pass (athena.apache.org: domain of harsh@cloudera.com designates
 209.85.192.173 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <869970D71E26D7498BDAC4E1CA92226B658DA8B1@MBX021-E3-NJ-2.exch021.domain.local>
References: 
 <869970D71E26D7498BDAC4E1CA92226B658DA8B1@MBX021-E3-NJ-2.exch021.domain.local>
From: Harsh J <harsh@cloudera.com>
Date: Sat, 6 Jul 2013 07:31:22 +0530
Message-ID: 
 <CAOcnVr3skf-ghRv9S5S3Y1JGtrRphSLebJRLj=cHtgH4oGUPvQ@mail.gmail.com>
Subject: Re: Accessing HDFS
To: "<user@hadoop.apache.org>" <user@hadoop.apache.org>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

These APIs (ClientProtocol, DFSClient) are not for Public access.
Please do not use them in production. The only API we care not to
change incompatibly are the FileContext and the FileSystem APIs. They
provide much of what you want - if not, log a JIRA.

On Fri, Jul 5, 2013 at 11:40 PM, John Lilley <john.lilley@redpoint.net> wro=
te:
> I=92ve seen mentioned that you can access HDFS via ClientProtocol, as in:
>
> ClientProtocol namenode =3D DFSClient.createNamenode(conf);
> LocatedBlocks lbs =3D namenode.getBlockLocations(path, start, length);
>
>
>
> But we use:
>
> fs =3D FileSystem.get(URI, conf);
>
> filestatus =3D fs.getFileStatus(path);
>
> fs.getFileBlockLocations(filestatus, start, length);
>
>
>
> As a YARN application and/or DFS client, are there times when I should us=
e
> the ClientProtocol directly?
>
>
>
> Thanks
>
> John
>
>


--=20
Harsh J