You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@cassandra.apache.org by kumar bharath <ku...@gmail.com> on 2019/05/14 17:29:34 UTC
Data Inconsistencies - Tables Vs Materialized Views.
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
Re: Data Inconsistencies - Tables Vs Materialized Views.
Posted by Alok Dwivedi <al...@instaclustr.com>.
Hi Bharat
As already pointed out below, there are some limitations and issues with Materialized views (depending upon your version). This blog post also summarizes some issues/caveats with MV
https://www.instaclustr.com/apache-cassandra-materialized-view-instaclustr-support/
Thanks
Alok Dwivedi
Senior Consultant
https://www.instaclustr.com/platform/
From: Avinash Mandava <av...@vorstella.com>
Reply-To: "user@cassandra.apache.org" <us...@cassandra.apache.org>
Date: Tuesday, 14 May 2019 at 18:47
To: "user@cassandra.apache.org" <us...@cassandra.apache.org>
Subject: Re: Data Inconsistencies - Tables Vs Materialized Views.
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 <ku...@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
Re: Data Inconsistencies - Tables Vs Materialized Views.
Posted by Avinash Mandava <av...@vorstella.com>.
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 <ku...@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
>