All of Hadoop's javadocs were recently lost from our website when it
was converted to svnpubsub.  These were historically not stored in
subversion but manually added to the website by release managers.
When the site was converted to svnpubsub no one had first copied the
docs tree into subversion so it was lost.  (It could perhaps be
recovered from tape archives, but that would be a pain.)

Yesterday, on seeing this, I reconstructed what I could.  I extracted
documentation from the release tarballs of recent releases an pushed
it into subversion.  Those release tarballs did not seem to include
HDFS javadocs.

You've found two links to HDFS javadocs in what I restored, and those
links, as you note, are broken.  If someone has those javadocs or
wants to build them then they can be restored by committing them to
subversion under:

https://svn.apache.org/repos/asf/hadoop/common/site/main/publish/docs/r1.1.1/
https://svn.apache.org/repos/asf/hadoop/common/site/main/publish/docs/r1.0.4/

I've not seen (broken) links to HDFS documentation in the other more
recent releases whose documentation I restored.

An alternative might be to put a redirect in to the HDFS user guide to
fix those two broken links.  If folks prefer that approach I'd be
happy to implement it.

Doug

On Thu, Feb 14, 2013 at 3:48 PM, Andrew Wang <andrew.w...@cloudera.com> wrote:
> Hi all,
>
> I think something changed recently regarding the online HDFS javadocs. I'm
> fairly sure they used to be available online, since it's indexed by google:
>
> https://www.google.com/?q=inurl:distributedfilesystem++site%3Ahadoop.apache.org
>
> However, all of those results 404 now.
>
> Going to the current API doc page (
> http://hadoop.apache.org/docs/current/api/), the "Hadoop Distributed
> FileSystem 
> (HDFS)<http://hadoop.apache.org/docs/current/api/org/apache/hadoop/hdfs/package-summary.html>"
> link also 404's:
>
> http://hadoop.apache.org/docs/current/api/org/apache/hadoop/hdfs/package-summary.html
>
> Is this an intended change? I at least found it really handy to have this
> stuff indexed and available online, even if they aren't user-facing APIs.
>
> Best,
> Andrew

Reply via email to