Return-Path: 
 <user-return-44644-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 61EBECE3C
	for <apmail-cassandra-user-archive@www.apache.org>;
 Wed,  7 Jan 2015 21:52:25 +0000 (UTC)
Received: (qmail 52895 invoked by uid 500); 7 Jan 2015 21:52:23 -0000
Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org
Received: (qmail 52854 invoked by uid 500); 7 Jan 2015 21:52:23 -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 52834 invoked by uid 99); 7 Jan 2015 21:52:23 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 07 Jan 2015 21:52:23 +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 bewang.tech@gmail.com
 designates 209.85.218.48 as permitted sender)
Received: from [209.85.218.48] (HELO mail-oi0-f48.google.com) (209.85.218.48)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 07 Jan 2015 21:51:57 +0000
Received: by mail-oi0-f48.google.com with SMTP id u20so4820430oif.7;
        Wed, 07 Jan 2015 13:49:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:date:message-id:subject:from:to:content-type;
        bh=B4TLcjesTmt14y4402Vjle+tnpIBcFR6ZLtrb1C0nDE=;
        b=SDXs7sos8eu2JAyPVzK48OX8CusfKab6TXjXBxK6chABtW3YZYDLvHL2y5+07sZvco
         2SdC6lUkTgt8ZgDlh3b/MuPYcGgnkagGwvABWeOqXQiwwKiHBTjPuU46j4RlFF4WYC4x
         oYDb+olNta2/Pdbz8IPOrKBbd5TULvkrv7BJJ1Jhzue53HlxkAhX+jtqeYwjwPLJ4JVl
         kXLdSK6VrHgc1ImrR1FpuDymJV6jiy9E8RpNapgBazpaD1w5vknXFXsR2OtVIz72GNaa
         olnlKpqbGuMS0bM5ubLkO4A0id8O9qHh+LlI2XeSH/CQUNB+wT+pBmQuVBvz9peBZGmQ
         YDLQ==
MIME-Version: 1.0
X-Received: by 10.202.197.132 with SMTP id v126mr3384028oif.2.1420667380482;
 Wed, 07 Jan 2015 13:49:40 -0800 (PST)
Received: by 10.202.106.208 with HTTP; Wed, 7 Jan 2015 13:49:40 -0800 (PST)
Date: Wed, 7 Jan 2015 13:49:40 -0800
Message-ID: 
 <CAMoVmf_1afkiJ16RxdOpQ3nP3Q1=YZ6ccg9LOafr84FjPoma3Q@mail.gmail.com>
Subject: Is it possible to delete columns or row using CQLSSTableWriter?
From: Benyi Wang <bewang.tech@gmail.com>
To: user@cassandra.apache.org, dev@cassandra.apache.org
Content-Type: multipart/alternative; boundary=001a1134e6608eca71050c16e670
X-Virus-Checked: Checked by ClamAV on apache.org

--001a1134e6608eca71050c16e670
Content-Type: text/plain; charset=UTF-8

CQLSSTableWriter only accepts an INSERT or UPDATE statement. I'm wondering
whether make it accept DELETE statement.

I need to update my cassandra table with a lot of data everyday.

* I may need to delete a row (given the partition key)
* I may need to delete some columns. For example, there are 20 rows for a
primary key before loading, the new load may have 10 rows only.

Because CQLSSTableWriter will write into a blank table, will DELETE put a
tombstone in the table so that the row in the server will be deleted after
bulk loading?

Thanks.

--001a1134e6608eca71050c16e670
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">CQLSSTableWriter only accepts an INSERT or UPDATE statemen=
t. I&#39;m wondering whether make it accept DELETE statement.<div><br></div=
><div>I need to update my cassandra table with a lot of data everyday.=C2=
=A0</div><div><br></div><div>* I may need to delete a row (given the partit=
ion key)</div><div>* I may need to delete some columns. For example, there =
are 20 rows for a primary key before loading, the new load may have 10 rows=
 only.</div><div><br></div><div>Because CQLSSTableWriter will write into a =
blank table, will DELETE put a tombstone in the table so that the row in th=
e server will be deleted after bulk loading?</div><div><br></div><div>Thank=
s.</div></div>

--001a1134e6608eca71050c16e670--