[jira] [Commented] (CASSANDRA-18312) Drop support for sstable formats before `na`
[
https://issues.apache.org/jira/browse/CASSANDRA-18312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17700552#comment-17700552
]
Michael Semb Wever commented on CASSANDRA-18312:
dev@ thread: https://lists.apache.org/thread/bxg30nol25oxf1hvpkrqobopxszrnor2
> Drop support for sstable formats before `na`
>
>
> Key: CASSANDRA-18312
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18312
> Project: Cassandra
> Issue Type: Task
> Components: Local/SSTable
>Reporter: Michael Semb Wever
>Assignee: Michael Semb Wever
>Priority: Normal
> Fix For: 5.x
>
>
> From 5.0 sstable formats before {{\-na\-}} are unsupported.
> This patch cleans up code related to the older formats.
> https://github.com/apache/cassandra/compare/trunk...thelastpickle:cassandra:mck/18312/trunk
>
> Raises the question whether backward compatibility to the previous major is
> defined by the Cassandra version or by the internal component version
> (sstable format).
> Also raises the question on whether downstream forks are wanting to support
> such upgrade paths, e.g. offline, and to what versions the {{sstableupgrade}}
> tool supports. This also touches on recent discussions around
> [Downgradability|https://lists.apache.org/thread/tcp339k5ph8ql35wxr085to4qgp8tpg7].
>
--
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
[jira] [Commented] (CASSANDRA-18312) Drop support for sstable formats before `na`
[
https://issues.apache.org/jira/browse/CASSANDRA-18312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17698450#comment-17698450
]
Michael Semb Wever commented on CASSANDRA-18312:
bq. When did we agree this?
The statement is indeed questioned in the description.
bq. This should have a DISCUSS thread.
There will be, as mentioned in the epic's description.
> Drop support for sstable formats before `na`
>
>
> Key: CASSANDRA-18312
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18312
> Project: Cassandra
> Issue Type: Task
> Components: Local/SSTable
>Reporter: Michael Semb Wever
>Assignee: Michael Semb Wever
>Priority: Normal
> Fix For: 5.x
>
>
> From 5.0 sstable formats before {{\-na\-}} are unsupported.
> This patch cleans up code related to the older formats.
> https://github.com/apache/cassandra/compare/trunk...thelastpickle:cassandra:mck/18312/trunk
>
> Raises the question whether backward compatibility to the previous major is
> defined by the Cassandra version or by the internal component version
> (sstable format).
> Also raises the question on whether downstream forks are wanting to support
> such upgrade paths, e.g. offline, and to what versions the {{sstableupgrade}}
> tool supports. This also touches on recent discussions around
> [Downgradability|https://lists.apache.org/thread/tcp339k5ph8ql35wxr085to4qgp8tpg7].
>
--
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
[jira] [Commented] (CASSANDRA-18312) Drop support for sstable formats before `na`
[
https://issues.apache.org/jira/browse/CASSANDRA-18312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17698445#comment-17698445
]
Benedict Elliott Smith commented on CASSANDRA-18312:
bq. From 5.0 sstable formats before -na- are unsupported.
When did we agree this? This should have a DISCUSS thread.
> Drop support for sstable formats before `na`
>
>
> Key: CASSANDRA-18312
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18312
> Project: Cassandra
> Issue Type: Task
> Components: Local/SSTable
>Reporter: Michael Semb Wever
>Assignee: Michael Semb Wever
>Priority: Normal
> Fix For: 5.x
>
>
> From 5.0 sstable formats before {{\-na\-}} are unsupported.
> This patch cleans up code related to the older formats.
> https://github.com/apache/cassandra/compare/trunk...thelastpickle:cassandra:mck/18312/trunk
>
> Raises the question whether backward compatibility to the previous major is
> defined by the Cassandra version or by the internal component version
> (sstable format).
> Also raises the question on whether downstream forks are wanting to support
> such upgrade paths, e.g. offline, and to what versions the {{sstableupgrade}}
> tool supports. This also touches on recent discussions around
> [Downgradability|https://lists.apache.org/thread/tcp339k5ph8ql35wxr085to4qgp8tpg7].
>
--
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
