[
https://issues.apache.org/jira/browse/CASSANDRA-19130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18005184#comment-18005184
]
Stefan Miklosovic commented on CASSANDRA-19130:
-----------------------------------------------
Aha, that's an interesting take about that syntactic sugar approach. So DROP +
CREATE is on TCM already hence whole TRUNCATE would be on TCM as well? It is
true that the result of DROP + CREATE is an empty table with same name but it
is not entirely same as this approach would create a new table with different
ID etc (unless we want to reuse it?). It would also most probably need to go
via different code path as from user's perspective or whoever is subscribing to
that it would look like every TRUNCATE would delete and create a table, no?
> 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]
