Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/468#issuecomment-42096004
@srowen I'd prefer not to remove it from the dependency graph if possible
because it will break local builds. The best solution I see is to add a profile
for Hadoop 2.3 and 2.4. For now I'd be fine to just require users to manually
trigger it and document this in `building-with-maven`. In SBT we can actually
just insert logic in the build based on the Hadoop profile. I'm guessing we'll
have to get into the habit of doing this, since it seems like Spark is good at
finding bugs in Hadoop's dependency graph. We should probably start testing
Spark against Hadoop RC's if they publish them to maven so we can give feedback.
I don't quite understand why the hadoop-client library doesn't advertise
jets3 specifically... if I write a Java application that opens an S3 FileSystem
and reads and writes data, don't I need jets3 to do that (i.e if this is
outside a MapReduce job)? Is this just a bug hadoop's dependencies?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
