... | ... | @@ -24,7 +24,7 @@ As we are getting closer to upcoming 2.0.0 release, the new features are fewer a |
|
|
|
|
|
## Incompatible Changes
|
|
|
|
|
|
1. **Deprecate Cassandra** - The Cassandra support is now deprecated. If you use it - don't panic. The only technical change now is that Kea will print a warning about the feature being deprecated, but will otherwise function as before. Cassandra code will remain intact in the remainder of the development 1.9.x and upcoming stable 2.0.x series. We are looking at removing it some time during the development 2.1.x series. The 2.2.x is foreseen to be the first stable branch with the Cassandra support removed. This effectively means that users have well over a year to think about their migration strategy. There is a new Section `3.8 Deprecated Features` in the ARM that discusses the technical and business reasons why we decided to deprecate Cassandra. Briefly, Cassandra's very different data model compared to other backends, namely MySQL and PostgreSQL, made it an ongoing maintenance and development pain, some concepts simply couldn't be implemented as it was not the right tool to solve some of the DHCP problems. It was also by far the least popular backend.
|
|
|
1. **Deprecate Cassandra** - The Cassandra support is now deprecated. If you use it - don't panic. The only technical change for now is that Kea will print a warning about the feature being deprecated, but will otherwise function as before. Cassandra code will remain intact in the remainder of the development 1.9.x and upcoming stable 2.0.x series. We are looking at removing it some time during the development 2.1.x series. The 2.2.x is foreseen to be the first stable branch with the Cassandra support removed. This effectively means that users have well over a year to think about their migration strategy. There is a new Section `3.8 Deprecated Features` in the ARM that discusses the technical and business reasons why we decided to deprecate Cassandra. Briefly, Cassandra's very different data model compared to other backends, namely MySQL and PostgreSQL, made it an ongoing maintenance and development pain, some concepts simply couldn't be implemented as it was not the right tool to solve some of the DHCP problems. Also, there are many warning signs that Cassandra project is having difficulties: packages for popular systems are not available, the C++ wrapper had a note about being in maintenance only for a while, the release versions of Cassandra require obsolete python 2 (with the python 3 support being available in unreleased alpha versions of Cassandra), they don't work with Java 11 (and require outdated Java 8) and more. It was also by far the least popular backend.
|
|
|
|
|
|
## Known Issues
|
|
|
|
... | ... | |