spark-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sean Owen (JIRA)" <>
Subject [jira] [Commented] (SPARK-22851) Download mirror for spark-2.2.1-bin-hadoop2.7.tgz has file with incorrect checksum
Date Fri, 22 Dec 2017 01:42:01 GMT


Sean Owen commented on SPARK-22851:

That I don't know. It would be at best an ASF INFRA question. yes, not resolved, just not
something to pursue here.

> Download mirror for spark-2.2.1-bin-hadoop2.7.tgz has file with incorrect checksum
> ----------------------------------------------------------------------------------
>                 Key: SPARK-22851
>                 URL:
>             Project: Spark
>          Issue Type: Bug
>          Components: Spark Core
>    Affects Versions: 2.2.1
>            Reporter: John Brock
>            Priority: Critical
> The correct sha512 is:
> 349ee4bc95c760259c1c28aaae0d9db4146115b03d710fe57685e0d18c9f9538d0b90d9c28f4031ed45f69def5bd217a5bf77fd50f685d93eb207445787f2685.
> However, the file I downloaded from
is giving me a different sha256:
> 039935ef9c4813eca15b29e7ddf91706844a52287999e8c5780f4361b736eb454110825224ae1b58cac9d686785ae0944a1c29e0b345532762752abab9b2cba9
> It looks like this mirror has a file that isn't actually gzipped, just tarred. If I ungzip
one of the copies of spark-2.2.1-bin-hadoop2.7.tgz with the correct sha512, and take the sha512
of the resulting tar, I get the same incorrect hash above of 039935ef9c4813eca15b29e7ddf91706844a52287999e8c5780f4361b736eb454110825224ae1b58cac9d686785ae0944a1c29e0b345532762752abab9b2cba9.
> I asked some colleagues to download the incorrect file themselves to check the hash --
some of them got a file that was gzipped and some didn't. I'm assuming there's some caching
or mirroring happening that may give you a different file than the one I got.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message