Thanks James, there were no hints pending at the time of dropping the materialized view. But the when we dropped the materialized view it somehow corrupted the hints.
On Fri, May 15, 2020 at 4:15 PM James Shaw <jxys...@gmail.com> wrote: > Surbhi: > I don't think you may truncate the materialized view. > What exact error got ? If you think it is same as the bug, then you may > try to avoid the bug triggered condition. It says pending hints. So you may > let all hints applied, then try drop the view. > > Thanks, > > James > > On Fri, May 15, 2020 at 1:35 PM Surbhi Gupta <surbhi.gupt...@gmail.com> > wrote: > >> Anyone has truncated materialized views ? >> >> On Thu, 14 May 2020 at 11:59, Surbhi Gupta <surbhi.gupt...@gmail.com> >> wrote: >> >>> Hi, >>> >>> We are on 3.11.0 . >>> We have 11 Materialized view on a table. >>> After discussion with application team , we found out that they are >>> using only 4 out of 11 . >>> We tried to drop the materialized view and got hit by the bug >>> https://issues.apache.org/jira/browse/CASSANDRA-13696 which made our >>> whole cluster unstable and multiple nodes were down at the same time . >>> >>> We will upgrade this cluster but my question is , can we truncate the >>> Materialized view rather than dropping? >>> >>> How will it impact ? >>> Does update into base table , updates all materialized views (This is my >>> understanding) ? >>> If yes, then truncate the data from the materialized view will create >>> too many read repairs later, correct? >>> Please correct me if I am wrong . >>> >>> Thanks >>> Surbhi >>> >>>
