[
https://issues.apache.org/jira/browse/CASSANDRA-18983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sam Tunnicliffe updated CASSANDRA-18983:
----------------------------------------
Status: Ready to Commit (was: Review In Progress)
+1
> Use epoch based table ids by default
> ------------------------------------
>
> Key: CASSANDRA-18983
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18983
> Project: Cassandra
> Issue Type: Improvement
> Components: Transactional Cluster Metadata
> Reporter: Sam Tunnicliffe
> Assignee: Marcus Eriksson
> Priority: Normal
> Attachments: ci_summary.html
>
>
> The initial implementation of CEP-21 depends on the use of deterministic
> table identifiers, as the table creation itself is performed by each node
> locally. This is suboptimal as recreating a previously dropped table can lead
> to the old data directory and files on disk, as well as CFIDs in the commit
> log being incorrectly associated with the new table.
> As the epoch gives us a unique identifier for each creation event, we can
> base the table id on that to ensure uniqueness.
> Implementation can be found in:
> https://github.com/beobal/cassandra/commit/89a0a2bfb0d1646e8057d9bb69f8ce558ef3b483
> CI summary results attached. For right now, we've only been foccussing on
> unit tests, in-jvm & python dtests, so the failures in other suites are to be
> expected. Unfortunately, the archive containing the detailed results is too
> large to attach as a single file, so will look into the best way to work
> around that.
> The intention is to fix all suites before merging the feature branch.
> ||Suite||Total||Passed||Skipped||Failed||Errors||
> |jvm dtest|1508|1465|24|8|11|
> |python dtest|1083|790|262|28|3|
> |unit|12082|12006|61|6|9|
--
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
