[
https://issues.apache.org/jira/browse/CASSANDRA-18301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17704259#comment-17704259
]
maxwellguo edited comment on CASSANDRA-18301 at 3/23/23 5:03 PM:
-----------------------------------------------------------------
If we support the ability for user to write specified version ，do we need to
add a tool to dynamic change the version，or do we permit to change this the
version？ If we do ，a new question is ，do we permit more than one version
sstable ‘s existence and what is the behavior of compaction ，read ，read repair
，repair and so on ；if we don‘t that means we can only use this every time we
restart the cluster？
besides some tools of Cassandra may only support high version，and if let user
write lower version ，it seems that some tools may fail for example
Cassandra-17698 ，though it is not checkin now .I think we at least shoul
support doc for these.
was (Author: maxwellguo):
If we support the ability for user to write specified version ，do we need to
add a tool to dynamic change the version，or do we permit to change this the
version？ If we do ，a new question is ，do we permit more than one version
sstable ‘s existence and what is the behavior of compaction ，read ，read repair
，repair and so on ；if we don‘t that means we can only use this every time we
restart the cluster？
> Let the user select the sstable version to write
> ------------------------------------------------
>
> Key: CASSANDRA-18301
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18301
> Project: Cassandra
> Issue Type: New Feature
> Components: Local/Config, Local/SSTable
> Reporter: Jacek Lewandowski
> Assignee: Jacek Lewandowski
> Priority: Normal
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
