[
https://issues.apache.org/jira/browse/CASSANDRA-18836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17763895#comment-17763895
]
Maxim Muzafarov commented on CASSANDRA-18836:
---------------------------------------------
I can take a look after I finish with CASSANDRA-16360
There are a few places where CRC32 is still used, but the main concern is that
it can affect backward compatibility, so it should be carefully considered.
> Replace CRC32 w/ CRC32C in IndexFileUtils.ChecksummingWriter
> ------------------------------------------------------------
>
> Key: CASSANDRA-18836
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18836
> Project: Cassandra
> Issue Type: Improvement
> Components: Feature/2i Index, Feature/SAI
> Reporter: Caleb Rackliffe
> Priority: Normal
>
> It seems that now we're on Java 11 for 5.0, there isn't much reason not to
> use CRC32C as a drop-in replacement for CRC32. SAI isn't even released, so
> has no binary compatibility entanglements, and this should be pretty
> straightforward.
> See https://github.com/apache/bookkeeper/pull/3309
--
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
