[
https://issues.apache.org/jira/browse/CASSANDRA-18301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17703757#comment-17703757
]
Jacek Lewandowski commented on CASSANDRA-18301:
-----------------------------------------------
[~bereng] what behaviour do you mean in particular?
I'm not sure I'm in favour of making it work like that - specify the Cassandra
version instead the exact sstable format version. I have my reasons:
- we still don't know which format implementation was used in the previous
version of Cassandra
- the user may want to enable other features while keep the old sstables format
version - after enabling other features but not bumping sstable format version,
the user is still able to go back. Without enabling other new features, the
user will not be able to evaluate a new version
> 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: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
