[
https://issues.apache.org/jira/browse/CASSANDRA-17582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17528145#comment-17528145
]
Jacek Lewandowski edited comment on CASSANDRA-17582 at 4/26/22 3:54 PM:
------------------------------------------------------------------------
https://github.com/apache/cassandra/pull/1591
https://app.circleci.com/pipelines/github/jacek-lewandowski/cassandra/215/workflows/032d9736-69e7-46e3-a61c-d63c87df3699
https://app.circleci.com/pipelines/github/jacek-lewandowski/cassandra/215/workflows/c43af657-f59b-480c-b108-091d6afe4dc1
was (Author: jlewandowski):
https://github.com/apache/cassandra/pull/1591
https://app.circleci.com/pipelines/github/jacek-lewandowski/cassandra/215/workflows/032d9736-69e7-46e3-a61c-d63c87df3699
> 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
> Fix For: 4.x
>
>
> 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-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
