spark-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Cody Koeninger <>
Subject Http client dependency conflict when using AWS
Date Mon, 10 Nov 2014 22:05:30 GMT
I'm wondering why

only updated the version of http client for the kinesis-asl profile and
left the base dependencies unchanged.

Spark built without that profile still has the same


when using aws components in general, not just kinesis (e.g.

Re-Reading the "Dependency Hell in Spark applications" thread from
september didn't shed any light on the subject.  As noted in that thread,
userClassPathFirst doesn't help.

Is there a reason not to depend on an updated version of httpclient for all
spark builds, as opposed to just kinesis-asl?

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message