7 ms·
Could be useful, it's a shame they're quite expensive to use on high-write tables.
by Sphax 11y ago
Could be useful, it's a shame they're quite expensive to use on high-write tables.
- arthursilva 11y agoI think it's a great usability improvement nonetheless. Sometimes you just need C* easy scalability (at least compared to the alternatives)
- _benedict 11y agoPerformance will be improved in later versions
- cowardlydragon 11y agoI'm guessing that materialized views can be sped up if the distribution of the component row keys can be mirrored across tables, so that the materialization can be treated as local and no internode communication is necessary. Having primary keys with identical node distribution keys is a recent set of commits...
- _benedict 11y agoYes, although that is probably useful for only a very limited subset of use-cases for materialized views. There are, however, more general purpose improvements to the approach that are just more involved to implement (and have their own negative performance risks, that would need to be balanced)
- dwenzek 11y agoYes this will be definitely useful, due to how eager is Cassandra of denormalized data ! See the comments a month ago about Cassandra data modeling (https://news.ycombinator.com/item?id=9728160 https://news.ycombinator.com/item?id=9728160). Even this example shows a materialized view per request !