[
https://issues.apache.org/jira/browse/CASSANDRA-13954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16207546#comment-16207546
]
Aleksey Yeschenko commented on CASSANDRA-13954:
-----------------------------------------------
Thanks!
Committed to 3.0 as
[d8a18f988f08de8504a45704632eff7f9494d82b|https://github.com/apache/cassandra/commit/d8a18f988f08de8504a45704632eff7f9494d82b]
and merged up with 3.11 and trunk. Dtest committed as
[f889dffe7489fad53085d46901fd7331f09600ba|https://github.com/apache/cassandra-dtest/commit/f889dffe7489fad53085d46901fd7331f09600ba].
> Provide a JMX call to sync schema with local storage
> ----------------------------------------------------
>
> Key: CASSANDRA-13954
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13954
> Project: Cassandra
> Issue Type: New Feature
> Components: Distributed Metadata
> Reporter: Aleksey Yeschenko
> Assignee: Aleksey Yeschenko
> Priority: Minor
> Fix For: 3.0.16, 3.11.2
>
>
> As discussed in CASSANDRA-13813 comments, we need such a call / nodetool
> command to enable the workaround for CASSANDRA-12701.
> This is technically a new feature and shouldn't go into 3.0.x, however in
> practical terms it's part of a solution to CASSANDRA-12701, which is a bug,
> and an pre-requisite for CASSANDRA-13813 - which is also a bug.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
