For local development , I set up Cassandra on my Macbook.
Considering that ScyllaDB now supports (experimental) MV (materialized view), it makes development easy. For the development server, I am running ScyllaDB on Ubuntu 16.04 hosted on Linod.
I faced the following problem:
>A few weeks later, one day, when I used the partition key to delete an entry from the base table (from ScyllaDB running on Ubuntu), the corresponding The MV still shows the corresponding entry of the deleted record.
After I gave up the entire Key-Space and recreated it, it was repaired, but I cannot determine the cause of this inconsistency.
>When I deleted When MV and recreated it, it didn’t copy the old data.
I tried to search, but couldn’t find a way to force MV to read from the base table and fill itself.
For the first question, I want to know if anyone has encountered a similar situation. Also, if there is anything I can do to prevent this from happening or cannot be prevented, this is the meaning of “experimental”.
Any help or References are appreciated.
When deciding on the technology stack of my own product, I decided to use the scyllaDB database because of its impressive performance.
For local development, I set up Cassandra on my Macbook.
Considering that ScyllaDB now supports (experimental) MV (materialized view), it makes development easy. For development server , I am running ScyllaDB on Ubuntu 16.04 hosted on Linod.
I am facing the following problem:
>A few weeks later, one day, when I use the partition key from the base table (from When deleting an entry in ScyllaDB running on Ubuntu, the corresponding MV still shows the corresponding entry of the deleted record.
After I gave up the entire Key-Space and recreated it, it was fixed, but I can’t be sure what caused it The reason for this inconsistency.
>When I deleted the MV and recreated it, it did not copy the old data.
I tried to search, but couldn’t find the forced MV from the base The table reads and fills in its own method.
For the first question, I would like to know if anyone has encountered a similar situation. Also, if there is anything I can do to prevent this from happening or It cannot be prevented, this is the meaning of “experimental”.
Any help or reference is appreciated.
In 2.1, Scylla lacks View construction (i.e. use existing data to populate the creation view), but this is resolved in 2.2.