diff --git a/docs/source/restore/restore-schema.rst b/docs/source/restore/restore-schema.rst index 28c76195a8..f25602a3ac 100644 --- a/docs/source/restore/restore-schema.rst +++ b/docs/source/restore/restore-schema.rst @@ -25,10 +25,6 @@ After successful restore it is important to perform necessary follow-up action. you should make a `rolling restart `_ of an entire cluster. Without the restart, the restored schema might not be visible, and querying it can return various errors. -It is recommended to drop all materialized views and secondary indexes that are part of the restored schema. -The next step, ``--restore-tables``, does not restore materialized views or secondary indexes. -It is the end user's responsibility to drop and recreate them after the tables have been successfully restored. - Process =======