You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Sylvain Lebresne (JIRA)" <ji...@apache.org> on 2010/11/18 09:24:14 UTC
[jira] Commented: (CASSANDRA-1753) SSTableImport adds columns
marked for delete incorrectly in methods addToStandardCF & addToSuperCF
[ https://issues.apache.org/jira/browse/CASSANDRA-1753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12933350#action_12933350 ]
Sylvain Lebresne commented on CASSANDRA-1753:
---------------------------------------------
+1
> SSTableImport adds columns marked for delete incorrectly in methods addToStandardCF & addToSuperCF
> --------------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-1753
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1753
> Project: Cassandra
> Issue Type: Bug
> Components: Tools
> Affects Versions: 0.7 beta 2
> Reporter: Pushpinder Heer
> Fix For: 0.7.0
>
> Attachments: cassandra-0.7-1753.txt
>
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> The logic for adding column families in the methods addToStandardCF & addToSuperCF appears to be backwards
> if (col.isDeleted) {
> cfamily.addColumn(path, hexToBytes(col.value), new TimestampClock(col.timestamp));
> } else {
> cfamily.addTombstone(path, hexToBytes(col.value), new TimestampClock(col.timestamp));
> }
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.