[GitHub] [cassandra] adelapena commented on pull request #1891: Cassandra 14227 trunk

["adelapena (via GitHub)" <gi...@apache.org>]

adelapena commented on PR #1891:
URL: https://github.com/apache/cassandra/pull/1891#issuecomment-1514862369

   So there is no boolean feature flag to control this. The behaviour rather depends on the sstable format, which is hardcoded on `BigFormat.BigVersion#current_version`. The hardcoded sstable version is the new `oa`, and it should work with other formats set by [CASSANDRA-18301](https://issues.apache.org/jira/browse/CASSANDRA-18301). We don't have tools to test this automatically on C, so it has been tested by manually changing the hardcoded sstable version. Is this correct?
   
   Is the plan to block this on CASSANDRA-18301? Or is it to commit this with the new major sstable version and make CASSANDRA-18301 a release blocker? IIUC the latter would involve merging with a couple of broken dtests and without full CI runs for sstable versions newer than `oa`.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: pr-unsubscribe@cassandra.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: pr-unsubscribe@cassandra.apache.org
For additional commands, e-mail: pr-help@cassandra.apache.org