You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Jacek Lewandowski (Jira)" <ji...@apache.org> on 2022/04/26 12:48:00 UTC

[jira] [Updated] (CASSANDRA-17582) Add missing information about whether to drop sstables or not when dropping schema objects

     [ https://issues.apache.org/jira/browse/CASSANDRA-17582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jacek Lewandowski updated CASSANDRA-17582:
------------------------------------------
    Test and Documentation Plan: run regression and the new test
                         Status: Patch Available  (was: Open)

> Add missing information about whether to drop sstables or not when dropping schema objects
> ------------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-17582
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-17582
>             Project: Cassandra
>          Issue Type: Task
>          Components: Local/SSTable
>            Reporter: Jacek Lewandowski
>            Assignee: Jacek Lewandowski
>            Priority: Normal
>
> This is the missed piece in SchemaChangeListener - when the implementation of SchemaUpdateHandler decides to say drop a table but keep sstables, that information about not-dropping sstables is not propagated to the SchemaChangeListener



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

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