Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Not A Problem
-
1.3.2, 1.4.0
-
None
Description
The published jars were always (or at least since 1.1.0, see SPARK-3764) published using hadoop 2 binaries.
However, the default are hadoop 1. Which means that an application that doesn't use hdfs will fail at simple functions like `saveAsObjectFile` (since it uses hadoop interfaces).
There are a couple of points that can be considered wrong here:
- it's not well stated that the published binaries aren't what you can expect base on spark rules w.r.t hadoop 1.0.4
- if an application doesn't need hdfs, the dev couldn't rely on public libraries, but he has to build it's own set without asking for a specific hadoop version (hence will get the 1.0.4) and deploy it on his own :-/