[ https://issues.apache.org/jira/browse/CASSANDRA-17582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex Petrov updated CASSANDRA-17582: ------------------------------------ Resolution: Fixed Status: Resolved (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: Improvement > Components: Local/SSTable > Reporter: Jacek Lewandowski > Assignee: Jacek Lewandowski > Priority: Normal > Fix For: 4.1-alpha1, 4.1 > > Time Spent: 10m > Remaining Estimate: 0h > > 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.10#820010) --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org