Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/2474#issuecomment-56932682
@JoshRosen It looks like HttpClient 4.1.3 comes in from Thrift via Hive:
```
mvn dependency:tree
...
[INFO] org.apache.spark:spark-hive_2.10:jar:1.2.0-SNAPSHOT
...
[INFO] +- org.spark-project.hive:hive-serde:jar:0.12.0:compile
[INFO] | +- org.spark-project.hive:hive-common:jar:0.12.0:compile
[INFO] | | +- org.spark-project.hive:hive-shims:jar:0.12.0:compile
[INFO] | | \- commons-cli:commons-cli:jar:1.2:compile
[INFO] | +- org.mockito:mockito-all:jar:1.9.0:test (version managed from
1.8.2; scope managed from compile)
[INFO] | \- org.apache.thrift:libfb303:jar:0.9.0:compile
[INFO] | \- org.apache.thrift:libthrift:jar:0.9.0:compile
[INFO] | +- org.apache.httpcomponents:httpclient:jar:4.1.3:compile
[INFO] | \- org.apache.httpcomponents:httpcore:jar:4.1.3:compile
```
... but that's weird if it has some effect on core tests, of course. This
could be a red herring, but that's where 4.1.3 may be coming from, and then
sticking around and getting put on some classpath.
This method went in late November 2012:
https://apache.googlesource.com/httpclient/+blame/ff1acb48a875b54319fed9da87d1942d4d0d9db3/httpclient/src/main/java/org/apache/http/impl/cookie/BrowserCompatSpecFactory.java
So would be in about version 4.2.3 or higher:
https://hc.apache.org/news.html
... which you probably already figured, that 4.1.3 (or some copy from
earlier than about 4.2.3) must be the problem. (I think that the 3.x artifacts
aren't an issue, because they're different artifacts.)
In your patch, you don't make `httpclient` a `test` scope dependency. I
would try that as I know the transitive dep rules are weird in `test` scope.
Maybe that actually forces the desired behavior. Try `mvn dependency:tree` as
well to get its opinion.
---
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.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
