Thanks Eric ... This is helpful...
On Wed, 12 Feb 2020 at 17:46, Erick Ramirez <erick.rami...@datastax.com> wrote: > There shouldn't be any negative impact from dropping MVs and there's > certainly no risk to the base table if that is your concern. All it will do > is remove all the data in the respective views plus drop any pending view > mutations from the batch log. If anything, you should see some performance > gain since updates to the base table will only trigger 4 view updates > instead of the previous 11. Cheers! > > Erick Ramirez | Developer Relations > > erick.rami...@datastax.com | datastax.com <http://www.datastax.com> > <https://www.linkedin.com/company/datastax> > <https://www.facebook.com/datastax> <https://twitter.com/datastax> > <http://feeds.feedburner.com/datastax> <https://github.com/datastax/> > > <https://www.datastax.com/accelerate> > > > > On Thu, 13 Feb 2020 at 04:26, Surbhi Gupta <surbhi.gupt...@gmail.com> > wrote: > >> Hi, >> >> So application team created 11 materialized views on a base table in >> production and we need to drop 7 Materialized views as they are not in use. >> Wanted to understand the impact of dropping the materialized views. >> We are on Cassandra 3.11.1 , multi datacenter with replication factor of >> 3 in each datacenter. >> We are using LOCAL_QUORUM for write consistency and LOCAL_ONE for read >> consistency. >> >> Any thoughts or suggestion to keep in mind before dropping the >> Materialized views. >> >> Thanks >> Surbhi >> >> >> >>
