[
https://issues.apache.org/jira/browse/CASSANDRA-21012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18116382#comment-18116382
]
Dmitry Konstantinov edited comment on CASSANDRA-21012 at 9/17/26 2:59 PM:
--------------------------------------------------------------------------
It looks like the test introduced in this ticket is failing on CI:
[^ci_summary.html]
Tests / test-latest jdk11 19/20 /
org.apache.cassandra.io.sstable.CQLSSTableWriterDaemonTest.testDefaultSSTableIdentifiersAreLegacy[backgroundWriteMode=standard]-latest_jdk11_x86_64
Tests / test-latest jdk11 19/20 /
org.apache.cassandra.io.sstable.CQLSSTableWriterDaemonTest.testDefaultSSTableIdentifiersAreLegacy[backgroundWriteMode=direct]-latest_jdk11_x86_64
Tests / test-latest jdk21 19/20 /
org.apache.cassandra.io.sstable.CQLSSTableWriterDaemonTest.testDefaultSSTableIdentifiersAreLegacy[backgroundWriteMode=standard]-latest_jdk21_x86_64
Tests / test-latest jdk21 19/20 /
org.apache.cassandra.io.sstable.CQLSSTableWriterDaemonTest.testDefaultSSTableIdentifiersAreLegacy[backgroundWriteMode=direct]-latest_jdk21_x86_64
Tests / test-latest jdk17 19/20 /
org.apache.cassandra.io.sstable.CQLSSTableWriterDaemonTest.testDefaultSSTableIdentifiersAreLegacy[backgroundWriteMode=standard]-latest_jdk17_x86_64
Tests / test-latest jdk17 19/20 /
org.apache.cassandra.io.sstable.CQLSSTableWriterDaemonTest.testDefaultSSTableIdentifiersAreLegacy[backgroundWriteMode=direct]-latest_jdk17_x86_64
was (Author: dnk):
It looks like the test introduced in this ticket are failing on CI:
[^ci_summary.html]
Tests / test-latest jdk11 19/20 /
org.apache.cassandra.io.sstable.CQLSSTableWriterDaemonTest.testDefaultSSTableIdentifiersAreLegacy[backgroundWriteMode=standard]-latest_jdk11_x86_64
Tests / test-latest jdk11 19/20 /
org.apache.cassandra.io.sstable.CQLSSTableWriterDaemonTest.testDefaultSSTableIdentifiersAreLegacy[backgroundWriteMode=direct]-latest_jdk11_x86_64
Tests / test-latest jdk21 19/20 /
org.apache.cassandra.io.sstable.CQLSSTableWriterDaemonTest.testDefaultSSTableIdentifiersAreLegacy[backgroundWriteMode=standard]-latest_jdk21_x86_64
Tests / test-latest jdk21 19/20 /
org.apache.cassandra.io.sstable.CQLSSTableWriterDaemonTest.testDefaultSSTableIdentifiersAreLegacy[backgroundWriteMode=direct]-latest_jdk21_x86_64
Tests / test-latest jdk17 19/20 /
org.apache.cassandra.io.sstable.CQLSSTableWriterDaemonTest.testDefaultSSTableIdentifiersAreLegacy[backgroundWriteMode=standard]-latest_jdk17_x86_64
Tests / test-latest jdk17 19/20 /
org.apache.cassandra.io.sstable.CQLSSTableWriterDaemonTest.testDefaultSSTableIdentifiersAreLegacy[backgroundWriteMode=direct]-latest_jdk17_x86_64
> Make CQLSSTableWriter to be able to specify id's of created tables (legacy /
> uuid)
> ----------------------------------------------------------------------------------
>
> Key: CASSANDRA-21012
> URL: https://issues.apache.org/jira/browse/CASSANDRA-21012
> Project: Apache Cassandra
> Issue Type: Improvement
> Components: Legacy/Core, Legacy/Tools
> Reporter: Stefan Miklosovic
> Assignee: Arvind Kandpal
> Priority: Normal
> Fix For: 7.0
>
> Attachments: ci_summary.html
>
> Time Spent: 2.5h
> Remaining Estimate: 0h
>
> There is no way to specify that a user wants SSTables to be created with UUID
> identifiers (as introduced / backed by uuid_sstable_identifiers_enabled: true
> flag in cassandra.yaml).
> We have evaluated that this is not necessary for Cassandra Analytics jobs
> because even they are created with legacy naming, they will be effectively
> renamed when SSTables are _imported_.
> However, if somebody looks for writing SSTables programmatically by
> CQSSTableWriter, outside of the context of Cassandra Analytics, and they want
> to just dump such SSTables to a (running) node with
> {{uuid_sstable_identifiers_enabled: true}}, and then they either start a node
> or refresh it (nodetool refresh), SSTables are not "renamed".
> Hence, there should be a possibility to specify how we want to name our
> SSTables upon creation.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
