Return-Path: 
 <user-return-33786-apmail-cassandra-user-archive=cassandra.apache.org@cassandra.apache.org>
X-Original-To: apmail-cassandra-user-archive@www.apache.org
Delivered-To: apmail-cassandra-user-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 5FEE9F859
	for <apmail-cassandra-user-archive@www.apache.org>;
 Sun, 28 Apr 2013 20:40:18 +0000 (UTC)
Received: (qmail 22968 invoked by uid 500); 28 Apr 2013 20:40:15 -0000
Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org
Received: (qmail 22939 invoked by uid 500); 28 Apr 2013 20:40:15 -0000
Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:user-help@cassandra.apache.org>
List-Unsubscribe: <mailto:user-unsubscribe@cassandra.apache.org>
List-Post: <mailto:user@cassandra.apache.org>
List-Id: <user.cassandra.apache.org>
Reply-To: user@cassandra.apache.org
Delivered-To: mailing list user@cassandra.apache.org
Received: (qmail 22930 invoked by uid 99); 28 Apr 2013 20:40:15 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 28 Apr 2013 20:40:15 +0000
X-ASF-Spam-Status: No, hits=1.5 required=5.0
	tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: domain of john.sanda@gmail.com designates
 209.85.216.169 as permitted sender)
Received: from [209.85.216.169] (HELO mail-qc0-f169.google.com)
 (209.85.216.169)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 28 Apr 2013 20:40:09 +0000
Received: by mail-qc0-f169.google.com with SMTP id t2so2895781qcq.0
        for <user@cassandra.apache.org>; Sun, 28 Apr 2013 13:39:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:x-received:date:message-id:subject:from:to
         :content-type;
        bh=wtxqoTz14CLvN5azyWe8Xii2AA61e3eGEI2wJKwd6oo=;
        b=kJIO06u4kegjX3u/92DqpANYQSliSWZf1eGeBhy2fmA6g827J19cDlYtap/WB5aKQM
         D7ZI8KPwr45ndxw43Y3pm9GU5Czy9w/FXd0fBAAIbJpwS9JlNdQ5NDcXW8tI7cMHPJvO
         valRw5Y6ckRdlURQ8MfBgNS3ujP9PsQl9ohYS+w1r+S2uGp97nKZvk9dkuX2ptPg0ax9
         xdtHv2Uqw0KNmUfFYqH8hh9SgCfa7MRQxJYTdVQULh8bqSreByRKmT5SFpRn1lsjmwAH
         OeIqh4EPE2A721rmtIgU5W/A3di0SGT5fdP9CNRpRww+srZiD7Gf+VERWFzpu1Lkmc5J
         31vg==
MIME-Version: 1.0
X-Received: by 10.229.151.3 with SMTP id a3mr1970459qcw.9.1367181588750; Sun,
 28 Apr 2013 13:39:48 -0700 (PDT)
Received: by 10.49.49.163 with HTTP; Sun, 28 Apr 2013 13:39:48 -0700 (PDT)
Date: Sun, 28 Apr 2013 16:39:48 -0400
Message-ID: 
 <CA+BDQ7wfVzn7ENfq1pEKXL3kW7NsHZK=WzE_h_8mhCQ5_sFgQA@mail.gmail.com>
Subject: question about internode_compression
From: John Sanda <john.sanda@gmail.com>
To: user@cassandra.apache.org
Content-Type: multipart/alternative; boundary=e89a8f647851f1069404db71c49f
X-Virus-Checked: Checked by ClamAV on apache.org

--e89a8f647851f1069404db71c49f
Content-Type: text/plain; charset=ISO-8859-1

When internode_compression is enabled, will the compression algorithm used
be the same as whatever I am using for sstable_compression?


- John

--e89a8f647851f1069404db71c49f
Content-Type: text/html; charset=ISO-8859-1

<div dir="ltr">When internode_compression is enabled, will the compression algorithm used be the same as whatever I am using for sstable_compression?<br clear="all"><div><br></div><br>- John
</div>

--e89a8f647851f1069404db71c49f--