Return-Path: Delivered-To: apmail-incubator-cassandra-dev-archive@minotaur.apache.org Received: (qmail 92838 invoked from network); 3 Apr 2009 04:10:36 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 3 Apr 2009 04:10:36 -0000 Received: (qmail 17494 invoked by uid 500); 3 Apr 2009 04:10:36 -0000 Delivered-To: apmail-incubator-cassandra-dev-archive@incubator.apache.org Received: (qmail 17448 invoked by uid 500); 3 Apr 2009 04:10:36 -0000 Mailing-List: contact cassandra-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: cassandra-dev@incubator.apache.org Delivered-To: mailing list cassandra-dev@incubator.apache.org Received: (qmail 17431 invoked by uid 99); 3 Apr 2009 04:10:36 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 03 Apr 2009 04:10:36 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of jbellis@gmail.com designates 209.85.221.108 as permitted sender) Received: from [209.85.221.108] (HELO mail-qy0-f108.google.com) (209.85.221.108) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 03 Apr 2009 04:10:00 +0000 Received: by qyk6 with SMTP id 6so1767282qyk.32 for ; Thu, 02 Apr 2009 21:09:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=abt+jrFR8AZucub4M2jIygktVAqEKlcYXx0QckyaKAY=; b=nXB8JNxDmGMr4Ix2sqasfW77cTb+TrldXf6ii94W4q57GCWW4C3Oz3DOcK9QrQWaEa ly11ui9+gzCH5eeoDj1Ab4OxynIXnY5Dhj6VGDcUsfxVyI67pQZgxfND+NOUa4lxf8es MtBa1D1ZKBxQFcnwOvF1yGhKz4MhD0XkVRqSI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=yCROYluFyDJo9cLycbdA41My976Nuz5EPAmXxkiku38IfQHHSeo0j2383am/pqV5wf uymPh6P9YEjxg/OTjdt6t38u1ZPgy07aVstCynGo/0MElfH+jGGpS+ry/t0OGJ0Siq77 0qeMWdo7432a5Rm+3JOTUYpQKuifVHPv4mHYE= MIME-Version: 1.0 Received: by 10.229.85.17 with SMTP id m17mr358765qcl.43.1238731779627; Thu, 02 Apr 2009 21:09:39 -0700 (PDT) In-Reply-To: References: Date: Thu, 2 Apr 2009 23:09:39 -0500 Message-ID: Subject: Re: BinaryMemtable From: Jonathan Ellis To: cassandra-dev@incubator.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org That's FB's workaround for cassandra dealing poorly with mass insert / data import. The idea is you pre-serialize columnfamilies, and then attach them to keys w/ binarymemtable which then stores them to sstables w/o having to do any of the normal CF serialization work. AFAIK nobody outside of FB has any sample code tho. On Thu, Apr 2, 2009 at 11:07 PM, Jun Rao wrote: > > Could anyone explain the purpose of BinaryMemtable? From the code, it see= ms > that it's used to store some binary data per key. However, it's not clear > who is using it and for what purpose. Thanks, > > Jun > IBM Almaden Research Center > K55/B1, 650 Harry Road, San Jose, CA =A095120-6099 > > junrao@almaden.ibm.com