You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Ariel Weisberg (JIRA)" <ji...@apache.org> on 2018/02/07 04:13:00 UTC
[jira] [Comment Edited] (CASSANDRA-13816) Document and test CAS and
non-CAS batch behavior for deleting and inserting the same key
[ https://issues.apache.org/jira/browse/CASSANDRA-13816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16354942#comment-16354942 ]
Ariel Weisberg edited comment on CASSANDRA-13816 at 2/7/18 4:12 AM:
--------------------------------------------------------------------
The part where this isn't LHF is that I wasn't able to verify the difference in behavior with a unit test. I know the behavior is not as expected just from some comparisons done with some other data I can't share.
That's the reason I never made progress on this ticket. The increased difficulty dropping it down my priority list relative to its perceived value.
I would work with someone new on it though so it wouldn't be insurmountable.
was (Author: aweisberg):
The part where this isn't LHF is that I wasn't able to verify the difference in behavior with a unit test. I know the behavior is not as expected just from some comparisons done with some other data I can't share.
That's the reason I never made progress on this ticket. The increased difficulty dropping it down my priority list relative to its perceived value.
> Document and test CAS and non-CAS batch behavior for deleting and inserting the same key
> ----------------------------------------------------------------------------------------
>
> Key: CASSANDRA-13816
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13816
> Project: Cassandra
> Issue Type: Bug
> Components: Documentation and Website, Testing
> Reporter: Ariel Weisberg
> Assignee: Ariel Weisberg
> Priority: Minor
> Labels: lhf
> Fix For: 3.11.x, 4.x
>
>
> Add/verify unit tests for inserting and deleting the same key for cell deletion, partition deletion, and range tombstone deletion for both CAS and non-CAS batches.
> Don't change the existing behavior.
> The behavior differs between batch and CAS so in the both the CAS and batch documentation mention that the behavior is not consistent. Make sure it is visible in both high level and reference docs for that functionality.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org