This page is meant as a template for writing a CIP. To create a CIP choose Tools->Copy on this page and modify with your content and replace the heading with the next CIP number and a description of your issue. Replace anything in italics with your own description.
Current state: [One of "Under Discussion", "Accepted", "Rejected"]
Discussion thread: here
Released: <Cassandra Version>
Please keep the discussion on the mailing list rather than commenting on the wiki (wiki discussions get unwieldy fast).
Describe the problems you are trying to solve.
The intended client audience. Examples include data scientists, data engineers, library devs, devops, etc. A single CIP can have multiple target personas.
What must this allow users to do, that they can't currently.
What problem(s) is this proposal not designed to solve.
Describe the new thing you want to do in appropriate detail. This may be fairly extensive and have large subsections of its own. Or it may be a few sentences. Use judgement based on the scope of the change.
New or Changed Public Interfaces
Briefly list any new interfaces that will be introduced as part of this proposal or any existing interfaces that will be removed or changed. The purpose of this section is to concisely call out the public contract that will come along with this feature.
A public interface is any change to the following:
- native protocol (and CQL)
- gossip and the messaging service
- pluggable components (SPIs) like authorisation, triggers, ..?
- commitlog, hintlog, cache files
- sstables components
- jmx mbeans (including metrics)
- client tool classes
- command line tools and arguments
- operational routines
- Anything else that will likely break existing users in some way when they upgrade
Compatibility, Deprecation, and Migration Plan
- What impact (if any) will there be on existing users?
- If we are changing behavior how will we phase out the older behavior?
- If we need special migration tools, describe them here.
- When will we remove the existing behavior?
Describe in few sentences how the CIP will be tested. We are mostly interested in system tests (since unit-tests are specific to implementation details). How will we know that the implementation works as expected? How will we know nothing broke?
If there are alternative ways of accomplishing the same thing, what were they? The purpose of this section is to motivate why the design is the way it is and not some other way.