[
https://issues.apache.org/jira/browse/CASSANDRA-19130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17837875#comment-17837875
]
Stefan Miklosovic edited comment on CASSANDRA-19130 at 4/16/24 8:33 PM:
------------------------------------------------------------------------
[~aratnofsky] feel free to expand that patch in the direction you fancy if you
are interested in that. I am very open to the cooperation on this.
?? TCM, then in compaction remove entire SSTables with maxDataAge <=
truncatedAt, and remove all cells with earlier mutation timestamps. When we're
handling a Truncation transformation in TCM (via TableTruncationListener), kick
off a local truncation compaction??
isnt this quite a heavy operation? compacting as part of truncation? how would
that look like when a node is restarted and truncations are replayed? You would
compact on every such truncation record until all is replayed?
was (Author: smiklosovic):
[~aratnofsky] feel free to expand that patch in the direction you fancy if you
are interested in that. I am very open to the cooperation on this.
> Implement transactional table truncation
> ----------------------------------------
>
> Key: CASSANDRA-19130
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19130
> Project: Cassandra
> Issue Type: New Feature
> Components: Consistency/Coordination
> Reporter: Marcus Eriksson
> Assignee: Stefan Miklosovic
> 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: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
