Just to clarify one thing. I understand experimental features to be alpha / beta quality, and as such the guarantees of correctness to differ from the other features presented in the database. We should likely articulate this in the wiki and docs if we have not.
In the case of mv’s, since they began as a regular feature, obviously we don’t want a degradation in functionality on the feature, experimental or not. Our guarantees and codification of feature apis and functionality have historically taken the form of unit tests and dtests, which while limited in their ability to explore and test a state space do provide a minimal guarantee of api consistency that should be sufficient to maintain our contracts of correctness with experimental features. Sent from my iPhone > On Jun 30, 2020, at 6:40 PM, joshua.mcken...@gmail.com wrote: > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org For additional commands, e-mail: dev-h...@cassandra.apache.org
