The Kroxylicious project is very pleased to announce the release of Kroxylicious 0.7.0. See the Changelog for a list of changes and summary of Deprecations, Changes and Removals.
In this release, Kroxylicious dips its toes (or, should that be claws?) into the world of record validation. You can now ensure that the content your producers send adheres to the schema you expect. If a producer sends a record that doesn’t meet the expected schema, the producer will get an error response and the message won’t be delivered to the topic. Banish those poison messages from your topics for good! Read more about the use-case or dive right into the documentation. This is a preview feature and we are already thinking about enhancements. We’d love to hear your feedback. Thanks to Carles Arnal of the Apicurio project for all the work he put into this feature.
We had a request from the community to tweak how record encryption resolves its keys so that it was compatible with the FIPS certified JCE provider Bouncy Castle.
You’ll find binaries attached to the GitHub release, and available through Maven Central.
Docker images are hosted at quay.io/kroxylicious/kroxylicious
We are eager for any feedback, you can create an issue in GitHub if you have any problems or want a feature added.