Correct, this happens when the timestamp of the delete occurs after
the timestamp of the column update.

On Fri, Jun 24, 2011 at 5:40 AM, David Boxenhorn <da...@citypath.com> wrote:
> "it can cause index corruption IF the row delete timestamp is higher
> than the column update's."
>
> By "higher" you mean later, i.e. some modifications to a row, then delete?
>
> I have not seen this error in our logs, but it could happen. I have a
> process where I insert historical data into Cassandra, in batches.
> Modifying something, then deleting it is a normal scenario.
>
> On Fri, Jun 24, 2011 at 12:41 AM, Jim Ancona <j...@anconafamily.com> wrote:
>> I've reopened the issue. On our 0.7.6-2 cluster, system.log is filling
>> with repeated instances of the UnsupportedOperationException. When
>> we've attempted to restart a node, the restart fails with the same
>> exception. Luckily we found this as part of our pre-deploy testing of
>> 0.7.6, not in production, but this is not "mostly a non-problem" here.
>>
>> Jim
>>
>> On Thu, Jun 23, 2011 at 3:25 PM, Jonathan Ellis <jbel...@gmail.com> wrote:
>>> The patch probably applies as-is but I don't want to take any risks
>>> with 0.7 to solve what is mostly a non-problem.
>>>
>>> On Thu, Jun 23, 2011 at 2:16 PM, Jim Ancona <j...@anconafamily.com> wrote:
>>>> Is there any reason this fix can't be back-ported to 0.7?
>>>>
>>>> Jim
>>>>
>>>> On Thu, Jun 23, 2011 at 3:00 PM, Jonathan Ellis <jbel...@gmail.com> wrote:
>>>>> Sorry, 0.8.2 is correct.
>>>>>
>>>>> On Thu, Jun 23, 2011 at 1:36 PM, Les Hazlewood <l...@katasoft.com> wrote:
>>>>>> The issue has the fix version as 0.8.2, not 0.7.7.  Is that incorrect?
>>>>>> Cheers,
>>>>>> Les
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Jonathan Ellis
>>>>> Project Chair, Apache Cassandra
>>>>> co-founder of DataStax, the source for professional Cassandra support
>>>>> http://www.datastax.com
>>>>>
>>>>
>>>
>>>
>>>
>>> --
>>> Jonathan Ellis
>>> Project Chair, Apache Cassandra
>>> co-founder of DataStax, the source for professional Cassandra support
>>> http://www.datastax.com
>>>
>>
>

Reply via email to