See steps 1-3 in the description section of the issue below:
https://issues.apache.org/jira/browse/CASSANDRA-44
On 4 August 2010 09:27, David Boxenhorn wrote:
> When I change schema I need to delete the commit logs - otherwise I get a
> null pointer exception.
>
> Is there a way that I can forc
In both my cases the re-inserts have a higher timestamp.
On 7 April 2010 20:13, Jonathan Ellis wrote:
> Your re-insert needs to have a higher timestamp than the delete, this is
> normal.
>
> On Wed, Apr 7, 2010 at 12:25 PM, Matthew Grogan
> wrote:
> > I am seeing a simil
I am seeing a similar problem running on 0.6 rc1.
The data/logs have existed since 0.5.
If I insert a new row then delete and re-insert then it works fine.
If I delete a row that was created under 0.5 then delete and re-insert then
the insert silently fails.
I can delete the data/logs and start