Return-Path: Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: (qmail 15241 invoked from network); 28 Dec 2010 04:29:07 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 28 Dec 2010 04:29:07 -0000 Received: (qmail 68640 invoked by uid 500); 28 Dec 2010 04:29:04 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 68460 invoked by uid 500); 28 Dec 2010 04:29:04 -0000 Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@cassandra.apache.org Delivered-To: mailing list user@cassandra.apache.org Received: (qmail 68451 invoked by uid 99); 28 Dec 2010 04:29:04 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 28 Dec 2010 04:29:04 +0000 X-ASF-Spam-Status: No, hits=1.5 required=10.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,RFC_ABUSE_POST,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of roshandawrani@gmail.com designates 74.125.82.172 as permitted sender) Received: from [74.125.82.172] (HELO mail-wy0-f172.google.com) (74.125.82.172) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 28 Dec 2010 04:28:58 +0000 Received: by wyf23 with SMTP id 23so9238871wyf.31 for ; Mon, 27 Dec 2010 20:28:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=pvHV3h75Z95nr8i7pkOrkFzysXn0q8k+JoIs710zFxw=; b=GCl66Ojz7QOY2izdyYpG43G3z51u9/KhYz/tSy3X5yVfxAp6XUiJS5cSnBjuwgXuHP TK5NyfpePvLIZOURUavpilKhiUKJ4841abBGFWXXU5jEBD+1jXQyPV1gmZhc02IS3sZy 3CvdWUV0DCKSNTCzab6XIJHz0tlRQy8VhNO+s= 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 :cc:content-type; b=XM3EzGVdqOJcPudsyUBnRj1uabWMq66aap6J5ACCJyHOMptQ+O7hg0jL0Wcr9aIUiA lnaaRTOvAFkLgDdYlf0tqoXUm1Bz0Z4fxRYR3E2e8a7+smxIjKxaeqxISUNbEFvURplg vO487D2t+tpo6P8bYahhVZxpibjrUuXIHCiTA= MIME-Version: 1.0 Received: by 10.216.173.15 with SMTP id u15mr13526926wel.83.1293510517393; Mon, 27 Dec 2010 20:28:37 -0800 (PST) Received: by 10.216.13.5 with HTTP; Mon, 27 Dec 2010 20:28:37 -0800 (PST) In-Reply-To: References: Date: Tue, 28 Dec 2010 09:58:37 +0530 Message-ID: Subject: Re: The mutations to delete sub-columns can't be batched? From: Roshan Dawrani To: hector-users@googlegroups.com Cc: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=00163641691be70a43049870e2d4 X-Virus-Checked: Checked by ClamAV on apache.org --00163641691be70a43049870e2d4 Content-Type: text/plain; charset=ISO-8859-1 Hi, I think I may have found another oversight on the Hector API. OrderedRows has a convenient peekLast() method, but it is missing in OrderedSuperRows. I am trying to get the rows in a batched manner, and being able to peek at the last one to make it the start key of the next batch is convenient. Of-course, I am able to pick the last row in a not-so-convenient way, but the API should be symmetrical. On Mon, Dec 27, 2010 at 10:22 PM, Nate McCall wrote: > Huh. That appears to be an oversight on our part. I'll add an > addSubDeletion to the Mutator class in trunk. Thank you for bringing > this up. > > On Sun, Dec 26, 2010 at 10:47 PM, Roshan Dawrani > wrote: > > There doesn't really seem to be an inherent limitation in batching > > sub-column deletes. > > > > Pelops seem to be doing it - > > > http://pelops.googlecode.com/svn/trunk/src/org/wyki/cassandra/pelops/Mutator.java > > [deleteSubColumn() / deleteSubColumns()] > > > > Is it worth an improvement request on Hector? > > > > On Mon, Dec 27, 2010 at 10:07 AM, Roshan Dawrani < > roshandawrani@gmail.com> > > wrote: > >> > >> Which "No"? > >> > >> 1) No, it is "not" correct correct that they can't be batched, or > >> > >> 1) No, they can't be batched > >> > >> :-) > >> > >> > >> On Mon, Dec 27, 2010 at 10:04 AM, Jonathan Ellis > >> wrote: > >>> > >>> On Sun, Dec 26, 2010 at 9:14 AM, Roshan Dawrani < > roshandawrani@gmail.com> > >>> wrote: > >>> > Is it correct that mutations that delete subcolumns of a super column > >>> > can't > >>> > be batched - unlike inserts and deletes of normal columns? > >>> > >>> No. > >>> > >>> -- > >>> Jonathan Ellis > >>> Project Chair, Apache Cassandra > >>> co-founder of Riptano, the source for professional Cassandra support > >>> http://riptano.com > >> > >> > >> > >> -- > >> Roshan > >> Blog: http://roshandawrani.wordpress.com/ > >> Twitter: @roshandawrani > >> Skype: roshandawrani > >> > > > -- Roshan Blog: http://roshandawrani.wordpress.com/ Twitter: @roshandawrani Skype: roshandawrani --00163641691be70a43049870e2d4 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi,

I think I may have found another oversight on the Hector API.
OrderedRows has a convenient peekLast() method, but it is missing in O= rderedSuperRows.

I am trying to get the rows in a batched manner, an= d being able to peek at the last one to make it the start key of the next b= atch is convenient.

Of-course, I am able to pick the last row in a not-so-convenient way, b= ut the API should be symmetrical.


On = Mon, Dec 27, 2010 at 10:22 PM, Nate McCall <nate@riptano.com> wrote:
Huh. That appears= to be an oversight on our part. I'll add an
addSubDeletion to the Mutator class in trunk. Thank you for bringing
this up.

On Sun, Dec 26, 2010 at 10:47 PM, Roshan Dawrani
<roshandawrani@gmail.com> wrote:
> There doesn't really seem to be an inherent limitation in batching=
> sub-column deletes.
>
> Pelops seem to be doing it -
> http://pelops.googlecode.com/svn/= trunk/src/org/wyki/cassandra/pelops/Mutator.java
> [deleteSubColumn() / deleteSubColumns()]
>
> Is it worth an improvement request on Hector?
>
> On Mon, Dec 27, 2010 at 10:07 AM, Roshan Dawrani <roshandawrani@gmail.com>
> wrote:
>>
>> Which "No"?
>>
>> 1) No, it is "not" correct correct that they can't b= e batched, or
>>
>> 1) No, they can't be batched
>>
>> :-)
>>
>>
>> On Mon, Dec 27, 2010 at 10:04 AM, Jonathan Ellis <jbellis@gmail.com>
>> wrote:
>>>
>>> On Sun, Dec 26, 2010 at 9:14 AM, Roshan Dawrani <roshandawrani@gmail.com>
>>> wrote:
>>> > Is it correct that mutations that delete subcolumns of a = super column
>>> > can't
>>> > be batched - unlike inserts and deletes of normal columns= ?
>>>
>>> No.
>>>
>>> --
>>> Jonathan Ellis
>>> Project Chair, Apache Cassandra
>>> co-founder of Riptano, the source for professional Cassandra s= upport
>>> http://riptan= o.com
>>
>>
>>
>> --
>> Roshan
>> Blog: http://roshandawrani.wordpress.com/
>> Twitter: @roshandawrani
>> Skype: roshandawrani
>>
>



--
Roshan
B= log: http= ://roshandawrani.wordpress.com/
Twitter: @roshandawrani
Skype: roshandawrani

--00163641691be70a43049870e2d4--