You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Stefan Miklosovic (Jira)" <ji...@apache.org> on 2026/01/07 16:07:00 UTC
[jira] [Commented] (CASSANDRA-21092) Add --disable-zero-copy-streaming parameter to sstableloader
[ https://issues.apache.org/jira/browse/CASSANDRA-21092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18050425#comment-18050425 ]
Stefan Miklosovic commented on CASSANDRA-21092:
-----------------------------------------------
could we change the exception message of "Filter should not be serialized in old format" to something like "Filter should not be serialized in old format, use --disable-zero-copy-streaming parameter if you attempt to use sstableloader which loads 3.x SSTables".
The motivation behind that is that when I do it without that flag, it fails on that, but I just do not have any clue what to do next, as I am presumably not aware of the fact that there is some flag somewhere to use to workaround this.
> Add --disable-zero-copy-streaming parameter to sstableloader
> ------------------------------------------------------------
>
> Key: CASSANDRA-21092
> URL: https://issues.apache.org/jira/browse/CASSANDRA-21092
> Project: Apache Cassandra
> Issue Type: Bug
> Components: Tool/sstable
> Reporter: Paulo Motta
> Assignee: Paulo Motta
> Priority: Normal
> Time Spent: 20m
> Remaining Estimate: 0h
>
> When attempting to load legacy Cassandra 3.11 sstables into a Cassandra 5.0+ cluster using sstableloader, the operation fails with a StreamException when zero-copy streaming is enabled (which is the default behavior). The root cause is an assertion error {{java.lang.AssertionError: Filter should not be serialized in old format at org.apache.cassandra.utils.BloomFilter.serialize(BloomFilter.java:67)}} that was introduced by CASSANDRA-17056 when it landed in the 5.0 branch.
> This is a regression from Cassandra 4.0 and 4.1, where zero-copy streaming works fine with legacy sstables. The changes in 5.0 introduced stricter validation that rejects the old bloom filter serialization format used in 3.x sstables, causing the streaming operation to fail.
> I'm not comfortable in removing the assertion and making a special case to skip the assertion for sstableloader would be invasive so I propose adding a new flag --disable-zero-copy-streaming to overcome this issue.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org