|Line 157:||Line 157:|
| <div id="9">9</div>
| <div id="9">9</div>
| '''<span style="color:
| '''<span style="color:"></span>'''
Revision as of 18:05, 4 April 2013
- 1 Apache Hadoop 2.0
Apache Hadoop 2.0
Bring Apache Hadoop, the hottest open source big data platform, to Fedora, the hottest open source distribution. Fedora should be the best distribution for using Apache Hadoop.
- Name: Matthew Farrellee
- Email: email@example.com
|Matthew Farrellee||mattf||keeping track, integration testing||UTC-5|
- Targeted release: Fedora 20
- Last updated: 3 Apr 2013
- Percentage of completion: 5%
Apache Hadoop is a widely used, increasingly complete big data platform, with a strong open source community and growing ecosystem. The goal is to package and integrate the core of the Hadoop ecosystem for Fedora, allowing for immediate use and creating a base for the rest of the ecosystem.
Benefit to Fedora
The Apache Hadoop software will be packaged and integrated with Fedora. The core of the Hadoop ecosystem will be available with Fedora and provide a base for additional packages.
- Package the Apache Hadoop 2.0.2 software
- Package all dependencies needed for Apache Hadoop 2.0.2
- Skip package dependencies required for unit testing, record them in a dependency backlog for later cleanup
We are taking an iterative, depth-first approach to packaging. We do not have all the dependencies mapped out ahead of time.
Anyone who wants to help should find an available dependency below, edit the table changing the state to Active and packager to yourself.
While packaging a dependency, test dependencies can be skipped. Testing will be done via integration testing periodically during packaging and then after packaging completes. Test dependencies that are skipped must be added to the Skipped dependencies table below.
If you are lucky enough to pick a dependency that itself has unpackaged dependencies, identity the sub-dependencies and add them to the bottom of the Dependencies table below, change your current dependency to Blocked and repeat.
If your dependency is already packaged but the version is incompatible, contact the package owner and resolve the incompatibility in a mutually satisfactory way. For instance:
- If the version available in Fedora is older, explore updating the package. If that is not possible, explore creating a package that includes a version in its name, e.g. pkgnameXY. Ultimately, the most recent version in Fedora should have the name pkgname while older versions have pkgnameXY. It may take a full Fedora release to rationalize package names. Make a note in the Dependencies table.
- If the version you need is older than the packaged version, consider creating a patch to use the newer version. If a patch is not viable, proceed by packaging the dependency with a version in its name, e.g. pkgnameXY. Make a note in the Dependencies table.
|Available||free for someone to take|
|Active||actively being packaged|
|Blocked||pending packages for dependencies|
|Review||under review, include link to review BZ|
|ant||Available||VERSION INCOMPATIBILITY: Version 1.6 asked for, 1.8 currently packaged in Fedora. Needs to be inspected for api/functional incompatibilities|
|apache-commons-daemon||Available||Java import compilation error with existing package. Needs inspection|
|apache-commons-math||Available||Current apache-commons-math uses math3 in pom instead of math. Hadoop requests version 2.x. Needs inspection|
|bookkeeper||Available||Version 4.0 requested|
|gmaven||Blocked||RHBZ #864084||Version 1.0 requested, available 1.4 (but has a broken deps)|
|groovy||Review||RHBZ #858127||gil||1.5 requested, but 1.8 packaged in fedora. Possible moving forward 1.8 series will be known as groovy18 and groovy will be 2.x.|
|hsqldb||Available||1.8 in fedora, 2.0 requested. 2.2.8 packaged by gil, but seemingly no review request. Needs followup.|
|javax-servlet||Available||3.0 requested for glassfish groupID. Failed resolution. Needs investigation since other javax.servlet API packages should be available in Fedora (tomcat?).|
|jetty||Available||VERSION INCOMPATIBILITY: jetty8 packaged in Fedora, but 6.x requested. 6 and 8 are incompatible. Needs investigation|
|kfs||Available||gil has packaged 0.5, but no review request. kfs has become Quantcast qfs|
|maven-native||Review||RHBZ #864084||gil||Needs patch to build with java7|
|slf4j||Available||Package in fedora fails to match in dependency resolution. Needs inspection|
|tomcat-jasper||Active||rrati||Version 5.5.x requested. May be able to use jasper jar from tomcat6 or later.|
|[package name]||Available||RHBZ #XYZ||noone||[notes]|
|0||[jar name]||[package name]||Available||noone||Needed for tests by #N|
- mvn-rpmbuild utility will ONLY resolve from system repo
- mvn-local will resolve from system repo first then fallback to maven if unresolved
- can be used to find the delta between system repo packages available and missing dependencies that can be viewed in the .m2 local maven repo (find *.jar)
- reveals how JPP lookups are executing per dependency -> useful for finding gId,aId mismatches
- tells maven to skip test compilation
TODO: Template spec files to work from
TODO: Setup staging repository for sharing packages under review
How To Test
- TODO: NEEDS MORE DEFINITION
- yum install X Y Z across one or more nodes
- Setup a simple cluster by following TBD
- Run http://hadoop.apache.org/docs/stable/gridmix.html
For users who are interested in running Apache Hadoop on Fedora, they will find it available from Fedora Project yum repositories.
TODO: SPECIFICALLY PACKAGES X Y Z
No other packages currently depend on Apache Hadoop.
Completion of this feature will involve packaging numerous dependencies, see the Dependencies table. Some of the dependencies are already being packaged by others in the Fedora community. Where dependency overlap is found, a negotaition must occur to ensure a satisfactory version and package is available to all parties.
TODO: Is https://fedoraproject.org/wiki/Hypertable ?
With no packages depending on Apache Hadoop, none is necessary. The biggest risk is not completing packages for all dependencies. In that case, the feature can be removed from the release notes. The packaged dependencies should remain in the distribution. The feature can be pushed to the next Fedora release.