[
https://issues.apache.org/jira/browse/CASSANDRA-19130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18005179#comment-18005179
]
Abe Ratnofsky commented on CASSANDRA-19130:
-------------------------------------------
I'm not working on this anymore, and I don't think this is a blocker for
CASSANDRA-20761.
TCM enables safe table drop + re-create without the resurrection issues that
existed before, so I'm not totally convinced of the utility of "transactional"
(really "highly-available") truncate that uses its own path. I've prefer to
have TRUNCATE be syntactic sugar for DESCRIBE + DROP + CREATE, which already
have clear semantics consistent with other schema changes.
> Implement transactional table truncation
> ----------------------------------------
>
> Key: CASSANDRA-19130
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19130
> Project: Apache Cassandra
> Issue Type: New Feature
> Components: Consistency/Coordination
> Reporter: Marcus Eriksson
> Priority: Normal
> Fix For: 5.x
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> TRUNCATE table should leverage cluster metadata to ensure consistent
> truncation timestamps across all replicas. The current implementation depends
> on all nodes being available, but this could be reimplemented as a
> {{Transformation}}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
