[
https://issues.apache.org/jira/browse/HADOOP-9904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13752339#comment-13752339
]
André Kelpe commented on HADOOP-9904:
-------------------------------------
Is the deployment process of the tarballs/rpms etc. documented somewhere? I
would love to submit a patch for the scripts, but I am unable to find them.
> discoverability of release tarballs
> -----------------------------------
>
> Key: HADOOP-9904
> URL: https://issues.apache.org/jira/browse/HADOOP-9904
> Project: Hadoop Common
> Issue Type: Improvement
> Components: build
> Reporter: André Kelpe
>
> As part of the cascading (http://cascading.org) project, we are maintaining a
> vagrant based hadoop setup
> (https://github.com/Cascading/vagrant-cascading-hadoop-cluster). This setup
> downloads the hadoop tarball from a nearby mirror, when the user starts it
> up. The problem we are having, is that there is no easy way for a script to
> determine the file name of the current stable release tarball to download.
> When 1.2.1 became the new stable release the former stable release 1.1.2 was
> removed from the mirrors. This broke our setup, while that is not really
> necessary, if it would be discoverable, what the latest tarball is.
> There is a /stable directory, which contains the latest release, however the
> file names are changing every time. If there would be link in the directory,
> that is called hadoop-stable.tar.gz or a simple text file, that explains,
> what the latest stable release is, our setup would continue working, even if
> a new version or hadoop is released.
--
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
