You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Radim Kolar (JIRA)" <ji...@apache.org> on 2012/09/22 18:27:07 UTC
[jira] [Created] (CASSANDRA-4702) drop/create CF does not always
delete data
Radim Kolar created CASSANDRA-4702:
--------------------------------------
Summary: drop/create CF does not always delete data
Key: CASSANDRA-4702
URL: https://issues.apache.org/jira/browse/CASSANDRA-4702
Project: Cassandra
Issue Type: Bug
Affects Versions: 1.1.5
Environment: Windows XP
Reporter: Radim Kolar
I have failing test which is doing drop/create CF & insert data & update data and again. If there is some background activity on CF (like compaction) then drop CF does not delete all of its sstables. After recreate CF old data are still there.
old sstables might get removed at later time resulting in can not open sstable errors. I am not sure what causes this second error, but its probably related to previous test failure.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CASSANDRA-4702) drop/create CF does not always
delete data
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-4702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis resolved CASSANDRA-4702.
---------------------------------------
Resolution: Invalid
Use truncate instead.
> drop/create CF does not always delete data
> ------------------------------------------
>
> Key: CASSANDRA-4702
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4702
> Project: Cassandra
> Issue Type: Bug
> Affects Versions: 1.1.5
> Environment: Windows XP
> Reporter: Radim Kolar
>
> I have failing test which is doing drop/create CF & insert data & update data and again. If there is some background activity on CF (like compaction) then drop CF does not delete all of its sstables. After recreate CF old data are still there.
> old sstables might get removed at later time resulting in can not open sstable errors. I am not sure what causes this second error, but its probably related to previous test failure.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira