[SPARK-12065] Upgrade Tachyon from 0.8.1 to 0.8.2

[JoshRosen]

This commit upgrades the Tachyon dependency from 0.8.1 to 0.8.2.

[JoshRosen]

/cc @calvinjia

[calvinjia]

@JoshRosen
LGTM, thanks for updating this.

[SparkQA]

Test build #46933 has finished for PR 10054 at commit e5ecbe0.

• This patch fails Spark unit tests.
• This patch merges cleanly.
• This patch adds no public classes.

[JoshRosen]

Jenkins, retest this please.

[SparkQA]

Test build #46944 has finished for PR 10054 at commit e5ecbe0.

• This patch passes all tests.
• This patch merges cleanly.
• This patch adds no public classes.

[JoshRosen]

Hey, quick question: why do we need these exclusions? AFAIK tachyon-client is an uber-JAR which shades all of its dependencies: http://mvnrepository.com/artifact/org.tachyonproject/tachyon-client/0.8.2

[JoshRosen]

Hmm, I guess we need this because the tachyon-client JAR still declares compile-scope dependencies on the artifacts that it shades and relocates, which will result in Tachyon client's shaded dependencies being pulled in. I'm a bit confused about why the tachyon-client JAR is published with a non-dependency-reduced POM.

This is corroborated by #8577, which needed to add additional exclusions because of this.

[JoshRosen]

I've filed https://tachyon.atlassian.net/browse/TACHYON-1380 to ask Tachyon to change the handling of dependencies in this POM for future releases. For now, though, I've verified that we don't need to change any of these exclusions because the client's dependencies haven't changed, so I think this PR should be good to merge.

[JoshRosen]

Ah, there was some slight confusion here: I somehow parsed "Distribution of Tachyon client module with shaded packages in jar" as "shades all dependencies", which isn't true, so there's not an issue here. My bad.