[
https://issues.apache.org/jira/browse/CASSANDRA-18187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17682293#comment-17682293
]
Doug Rohrer commented on CASSANDRA-18187:
-----------------------------------------
Sadly, I forgot to take `localDeletionTime` into account in some of these tests
and, along with the way Cassandra handles multiple rows with the same PK by
lexicographical sorting (which is what made \{testWriteWithTtl} pass sometimes
but not others), made these test lest consistent and just plain wrong but in a
"but the test passes" way. I've updated them to be more specific and careful
with these issues, so it _should_ now be correct, but if there's any other
details I'm missing I'd appreciate a once-over.
> Add unit tests for per-row TTL and Timestamp usage in CQLSSTableWriter
> ----------------------------------------------------------------------
>
> Key: CASSANDRA-18187
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18187
> Project: Cassandra
> Issue Type: Improvement
> Components: Test/unit
> Reporter: Doug Rohrer
> Assignee: Doug Rohrer
> Priority: Low
> Fix For: 4.x
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> CQLSSTableWriter supports per-row setting of both timestamp and TTL values,
> but it’s not tested or documented today. Add tests to cover setting both TTL
> and Timestamp values for rows using the CQLSSTableWriter.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
