ScyllaDB 2.1-与物化视图不一致 [英] ScyllaDB 2.1 - Inconsistency with Materialized View

问题描述

在决定自己产品的技术堆栈时，由于其出色的性能，我决定将scyllaDB用于数据库.

While deciding on the technology stack for my own product, I decided to go with scyllaDB for database due to it's impressive performance.

对于本地开发，我在Macbook上设置了Cassandra.考虑到ScyllaDB现在支持(实验)MV(材料化视图)，因此使开发变得容易.对于开发服务器，我正在Linod上托管的Ubuntu 16.04上运行ScyllaDB.

For local development, I setup Cassandra on my Macbook. Considering ScyllaDB now supports (experimental) MV (Materialized View), it made the development easy. For dev server, I'm running ScyllaDB on Ubuntu 16.04 hosted on Linod.

我面临以下问题:

1. 几周后的一天，有一天，当我使用分区键从基本表(从在Ubuntu上运行的ScyllaDB)中删除条目时，相应的MV仍显示了已删除记录的相应条目.在删除整个键空间并重新创建它后，此问题已修复，但是我无法查明是什么原因导致了这种不一致.

1. After a few weeks, one day when I deleted an entry from base table (from ScyllaDB running on Ubuntu) using the partition key, the respective MV still showed the respective entry for the deleted record. It was fixed after I dropped the whole Key-Space and recreated it, but I'm unable to pinpoint what caused this inconsistency.

当我删除MV并重新创建它时，它没有复制旧数据.我尝试搜索，但是找不到强迫MV从基表读取并填充自身的方法.

When I dropped the MV and recreated it, it did not copy the old data. I tried to search, but could not find a way to force MV to read from base table and populate itself.

对于第一个问题，我想知道是否有人遇到过类似的情况.另外，如果我有什么办法可以防止这种情况的发生或无法避免，那就是实验性"的意思.

For the first issue, I would like to know if anyone faced similar scenario. Also if there is anything I can do to prevent this from happening or if it can't be prevented and that is what it means to be "experimental".

感谢任何帮助或参考.

推荐答案

在2.1版中，Sylla缺乏视图构建功能(即使用现有数据填充创建时的视图)，但是在2.2版中可以解决此问题.

In 2.1 Scylla lacked view building (that is, using existing data to populate a view on creation), but that is solved in 2.2.

这篇关于ScyllaDB 2.1-与物化视图不一致的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！