Hi Bharath, Not sure if you've seen the known limitations https://docs.datastax.com/en/cql/3.3/cql/cql_using/knownLimitationsMV.html <https://outrch.vorstella.com/api/mailings/click/PMRHK4TMEI5CE2DUORYHGORPF5SG6Y3TFZSGC5DBON2GC6BOMNXW2L3FNYXWG4LMF4ZS4MZPMNYWYL3DOFWF65LTNFXGOL3LNZXXO3SMNFWWS5DBORUW63TTJVLC42DUNVWCELBCNFSCEORUGY2SYITPOJTSEORCHA2TCNRXMRRDSLLCMIYGMLJUMM4DCLJZHFSDCLJXGFTDSMDBHE2TKMTDHERCYITWMVZHG2LPNYRDUIRUEIWCE43JM4RDUISTIJQVE3RQMZYXMZBSJVTHGWCNIE2XGU3QOJKGYNTHMJZVMMKYJY2WMOKFIVZGSSKQGBVT2IT5>
MV is one of those "supported, with caveats" things, do you think any of those issues linked above might be relevant on first look? Anything there ruled out from initial analysis? Or do you need some guidance on how to look for the right information to rule things out? On Tue, May 14, 2019 at 10:30 AM kumar bharath <kumar.bharathb...@gmail.com> wrote: > Hi All, > > I have an use case wherein we created two materialized views on top a > column family in Cassandra. We are facing data inconsistencies between > base table and materialized views created on top of it. > > Example: Deleted a record in base table about a month ago., Materialized > view are still showing that record. > > > Thanks, > Bharath Kumar B >
