There are numerous things I'd like to contribute to on the next roadmap. I really think that pluggable storage is a great goal and can expand Cassandra's options for performance and scalability, so I plan on helping to work on that.
I also plan to work on extending CQLSH so that it offers plugin support (particularly for security plugins). See https://issues.apache.org/jira/browse/CASSANDRA-16456. One idea I wanted to raise here is concerning testing. With all the many managed or tweaked Cassandra solutions available (such as DataStax Astra, Amazon Keyspaces, ScyllaDB, etc.), I would love to work on a suite of protocol tests that are isolated to testing CQL compatibility. Basically, a test tool that focuses on the CQL grammar (the kind of testing the pact framework does for example, https://docs.pact.io/getting_started/how_pact_works/). This would help test the CQL compatibility of any offering, help improve their support, and would help us be crisp about what is part of CQL and what is a different kind of addition. Assuming there is some interest in this, I plan on writing a CEP to cover the idea. Thanks! Brian Sent with ProtonMail Secure Email. ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Thursday, April 8, 2021 12:55 PM, David Capwell <dcapw...@apple.com.INVALID> wrote: > Here are two things I descoped from 4.0 and plan to pick up after 4.0 release > > https://issues.apache.org/jira/browse/CASSANDRA-15566 > https://issues.apache.org/jira/browse/CASSANDRA-15566 - Repair coordinator > can hang under some cases. Aka repair has many cases where it can become > unresponsive and not reliant; so work to improve it. > https://issues.apache.org/jira/browse/CASSANDRA-15399 > https://issues.apache.org/jira/browse/CASSANDRA-15399 - Add ability to track > state in repair. Rather than rely on logs to see what repair is doing, add > APIs to expose what’s going on with repair, and what repair has done. > > > On Apr 8, 2021, at 8:22 AM, Benjamin Lerer b.le...@gmail.com wrote: > > On our side, the list of improvements we plan to deliver for the next > > release are: > > Query side improvements: > > > > - Storage Attached Index or SAI. The CEP can be found at > > > > https://cwiki.apache.org/confluence/display/CASSANDRA/CEP-7%3A+Storage+Attached+Index > > > > - Add support for OR predicates in the CQL where clause > > - Allow to aggregate by time intervals (CASSANDRA-11871) and allow UDFs > > in GROUP BY clause > > > > - Materialized views hardening: Addressing the different Materialized > > Views issues (see CASSANDRA-15921 and [1] for some of the work involved) > > > > > > Security improvements: > > > > - Add support for Dynamic Data Masking (CEP pending) > > - Allow the creation of roles that have the ability to assign arbitrary > > privileges, or scoped privileges without also granting those roles > > access > > to database objects. > > > > - Filter rows from system and system_schema based on users permissions > > > > Performance improvements: > > > > - Trie-based index format (CEP pending) > > - Trie-based memtables (CEP pending) > > > > Safety/Usability improvements: > > > > - Guardrails. The CEP can be found at > > > > https://cwiki.apache.org/confluence/display/CASSANDRA/(DRAFT)+-+CEP-3%3A+Guardrails > > > > > > Pluggability improvements: > > > > - Pluggable schema manager (CEP pending) > > - Pluggable filesystem (CEP pending) > > - Memtable API (CEP pending). The goal being to allow improvements such > > as CASSANDRA-13981 to be easily plugged into Cassandra > > > > > > Feedbacks are welcome :-). > > [1] > > https://lists.apache.org/thread.html/r908b5397dd803132822cabe5ba0755861d97bb5d8603a523591d55c9%40<dev.cassandra.apache.org> > > Le jeu. 8 avr. 2021 à 17:21, Benjamin Lerer ble...@apache.org a écrit : > > > > > Hi Everybody, > > > Please speak up and tell us what you plan to contribute in the next year. > > > The goal of this discussion is to allow people to present the > > > contributions that they have planned for the next Cassandra release. > > > That discussion has several benefits: > > > > > > - It will give a greater visibility on who is planning to contribute > > > and what their contributions would be. Allowing other contributors to > > > join > > > the efforts or ask for questions if they wish to. > > > > > > - It will also us to synchronize our efforts when some features > > > impact the same part of the code > > > > > > - For users, it will provide an idea of what to expect from the next > > > release > > > > > > > > > Thanks in advance for all your inputs. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org For additional commands, e-mail: dev-h...@cassandra.apache.org
