Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Thu, 4 Jun 2015 16:10:38 +0000 (UTC)
From: "Mike Adamson (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12835447.1433434209000.12521.1433434238406@Atlassian.JIRA>
In-Reply-To: <JIRA.12835447.1433434209000@Atlassian.JIRA>
References: <JIRA.12835447.1433434209000@Atlassian.JIRA>
 <JIRA.12835447.1433434209339@arcas>
Subject: [jira] [Created] (CASSANDRA-9548) SnappyCompressor only works with
 direct buffers
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Mike Adamson created CASSANDRA-9548:
---------------------------------------

             Summary: SnappyCompressor only works with direct buffers
                 Key: CASSANDRA-9548
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9548
             Project: Cassandra
          Issue Type: Bug
          Components: Core
            Reporter: Mike Adamson
             Fix For: 2.2.0 rc1


The SnappyCompressor is reporting the following errors:
{noformat}
    org.xerial.snappy.SnappyError: [NOT_A_DIRECT_BUFFER] input is not a direct buffer
        at org.xerial.snappy.Snappy.compress(Snappy.java:143)
        at org.apache.cassandra.io.compress.SnappyCompressor.compress(SnappyCompressor.java:85)
{noformat}
This is because in 2.2 the SnappyCompressor is now calling
{noformat}
Snappy.compress
{noformat}
instead of (as previously)
{noformat}
Snappy.rawCompress
{noformat}
Snappy.compress checks that the input and output buffers are direct and throws the above error.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)