You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Sean Owen (JIRA)" <ji...@apache.org> on 2017/12/20 20:43:00 UTC
[jira] [Commented] (SPARK-22851) Download mirror for
spark-2.2.1-bin-hadoop2.7.tgz has file with incorrect checksum
[ https://issues.apache.org/jira/browse/SPARK-22851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16299059#comment-16299059 ]
Sean Owen commented on SPARK-22851:
-----------------------------------
I see the same thing. The source release seems fine but the binary release does not, and it seems indeed to not actually be gzipped. I suspect the hash is correct for the original gzipped tarball. I don't know why that would have happened; any ideas [~felixcheung] ? I missed it as I typically just check the source archive and let it go at that, as that's the main artifact.
It would definitely be weird if some mirrors had a gzipped archive and some not. Are you saying some people get this exact same file gzipped and some not? or found some files in the release were right and the others not? the latter is what I'm seeing.
> Download mirror for spark-2.2.1-bin-hadoop2.7.tgz has file with incorrect checksum
> ----------------------------------------------------------------------------------
>
> Key: SPARK-22851
> URL: https://issues.apache.org/jira/browse/SPARK-22851
> 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 http://apache.mirrors.pair.com/spark/spark-2.2.1/spark-2.2.1-bin-hadoop2.7.tgz 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
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org