incubator-cassandra-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Soo Hwan Park" <spark2...@cs.ucsb.edu>
Subject Re: remove doesn't work in the latest version
Date Tue, 07 Apr 2009 18:55:28 GMT
Thanks Jonathan, 
I'm running a cluster of 4 Cassandras over VMs. so, I need to consider a node failure case.

I'll look into the thread. 

Soo Hwan  

--------------------------------------------------
From: "Jonathan Ellis" <jbellis@gmail.com>
Sent: Tuesday, April 07, 2009 11:42 AM
To: <cassandra-dev@incubator.apache.org>
Subject: Re: remove doesn't work in the latest version

> It will work fine on a single node, and it will work in a cluster as
> long as you don't have node failures.  Jeff linked the thread where I
> discussed the distributed case in more detail.
> 
> -Jonathan
> 
> On Tue, Apr 7, 2009 at 1:10 PM, Soo Hwan Park <spark2007@cs.ucsb.edu> wrote:
>> Thanks for answers Jonathan, Sandeep, and Jeff,
>>
>> so I can use "public boolean remove(String tablename, String key, String columnFamily_column,
long timestamp, int block_for)" and
>> there are some issues that Avinash points out?
>>
>> What bad things could happen if I use the current "remove" ??
>> the issues of tombstones (deletion markers) were solved?
>> Could you explain?
>>
>>
>> Soo Hwan
>>
>> --------------------------------------------------
>> From: "Jonathan Ellis" <jbellis@gmail.com>
>> Sent: Tuesday, April 07, 2009 9:28 AM
>> To: <cassandra-dev@incubator.apache.org>
>> Subject: Re: remove doesn't work in the latest version
>>
>>> Those changes have been applied under the reasoning that at least it's
>>> _less_ broken than it was. :)
>>>
>>> All you need to do is expose
>>>
>>>    public boolean remove(String tablename, String key, String
>>> columnFamily_column, long timestamp, int block_for)
>>>
>>> to thrift.
>>>
>>> (Last I heard, Avinash was working on the CassandraServer / thrift
>>> interface area, so I have put this off until he commits to avoid
>>> adding conflicts for him.)
>>>
>>> On Tue, Apr 7, 2009 at 11:22 AM, Sandeep Tata <sandeep.tata@gmail.com>
wrote:
>>>> If you're okay with the problems Avinash points out with the current
>>>> remove solution, you may want to take a look at Jonathan's patch in
>>>> CASSANDRA-1. It may not apply as-is anymore, but shouldn't be too hard
>>>> to incorporate.
>>>>
>>>> On Tue, Apr 7, 2009 at 3:26 AM, Jeff Hammerbacher <hammer@cloudera.com>
wrote:
>>>>> Hey Soo Hwan,
>>>>>
>>>>> The discussion on why deletes are not currently handled in Cassandra
was
>>>>> conducted over email and not archived in a JIRA ticket. I recommend checking
>>>>> out the following thread on MarkMail:
>>>>> http://markmail.org/thread/f3bh23wbgjfn26xn.
>>>>>
>>>>> Regards,
>>>>> Jeff
>>>>>
>>>>> 2009/4/7 Soo Hwan Park <spark2007@cs.ucsb.edu>
>>>>>
>>>>>> Hmm.. remove is not supported right now (in the latest code)..
>>>>>> Could somebody explain why? (is it because of data consistency problem??)
>>>>>>
>>>>>> public void remove(String tablename, String key, String
>>>>>> columnFamily_column)
>>>>>>  {
>>>>>>  throw new UnsupportedOperationException("Remove is coming soon");
>>>>>>  }
>>>>>>
>>>>>> Thanks,
>>>>>> Soo Hwan
>>>>>
>>>> 
Mime
View raw message