[
https://issues.apache.org/jira/browse/CASSANDRA-18187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17682671#comment-17682671
]
Brandon Williams commented on CASSANDRA-18187:
----------------------------------------------
bq. The other option for this is to increase the TTL and the sleep time, but I
hate adding long sleeps in tests for obvious reasons, so I think removing the
initial check for 2 rows is reasonable here.
Test with TTLs are notoriously tricky due to this sort of thing, so I agree
with this.
||Branch||CI||
|[trunk|https://github.com/driftx/cassandra/tree/CASSANDRA-18187]|[j8|https://app.circleci.com/pipelines/github/driftx/cassandra/841/workflows/12c8a20b-18fa-45b7-83a6-ecc04eb5d668],
[j11|https://app.circleci.com/pipelines/github/driftx/cassandra/841/workflows/20988f4a-5947-4d59-92bc-21ba03b61b7b]|
> 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: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
