You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Josh Rosen (JIRA)" <ji...@apache.org> on 2014/10/24 02:57:33 UTC
[jira] [Updated] (SPARK-4056) Upgrade snappy-java to 1.1.1.5
[ https://issues.apache.org/jira/browse/SPARK-4056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Josh Rosen updated SPARK-4056:
------------------------------
Description:
We should upgrade snappy-java to 1.1.1.5 across all of our maintenance branches. This release improves error messages when attempting to deserialize empty inputs using SnappyInputStream (this operation is always an error, but the old error messages made it hard to distinguish failures due to empty streams from ones due to reading invalid / corrupted streams); see https://github.com/xerial/snappy-java/issues/89 for more context.
This should be a major help in the Snappy debugging work that I've been doing.
was:
We should upgrade snappy-java to 1.1.1.4 across all of our maintenance branches. This release improves error messages when attempting to deserialize empty inputs using SnappyInputStream (this operation is always an error, but the old error messages made it hard to distinguish failures due to empty streams from ones due to reading invalid / corrupted streams); see https://github.com/xerial/snappy-java/issues/89 for more context.
As soon as 1.1.1.4 is available from Maven Central (probably tomorrow), I'll submit a PR for this. This should be a major help in the Snappy debugging work that I've been doing.
Summary: Upgrade snappy-java to 1.1.1.5 (was: Upgrade snappy-java to 1.1.1.4)
> Upgrade snappy-java to 1.1.1.5
> ------------------------------
>
> Key: SPARK-4056
> URL: https://issues.apache.org/jira/browse/SPARK-4056
> Project: Spark
> Issue Type: Improvement
> Reporter: Josh Rosen
> Assignee: Josh Rosen
>
> We should upgrade snappy-java to 1.1.1.5 across all of our maintenance branches. This release improves error messages when attempting to deserialize empty inputs using SnappyInputStream (this operation is always an error, but the old error messages made it hard to distinguish failures due to empty streams from ones due to reading invalid / corrupted streams); see https://github.com/xerial/snappy-java/issues/89 for more context.
> This should be a major help in the Snappy debugging work that I've been doing.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org