Kadeck 5.2

Kadeck 5.2 extends our Data Policy features, adds support for Apple Silicon and more.

What's new

Kadeck 5.2 extends our Data Protection Policy features, adds support for Apple Silicon and ARM on Kadeck Desktop and Kadeck Teams, and improves our underlying streaming client.

Patch notes

This section contains all patch notes for Kadeck 5.2.x.

Release 5.2.3 (Hotfix)

  • Fixed a problem caused by incomplete topic monitoring data.
  • Fixed wrong offset calculation for partitions with 0 records.
  • Fixed wrong total record count.

Release 5.2.2

  • Data Protection Policies: Added key/value modes. Policies can now affect only keys, values, or both, allowing the use of String or CSV codecs for keys even if a data protection policy is in place for the value.
  • UI & UX: Many refinements for a better user experience.
  • Connection Info: Moved from main navigation to connection cards.
  • Data Catalog: Export, import, and create topic buttons moved to the header for smaller screens.
  • Topic List: New layout with views, favorites, and sections for better overview and easier navigation.
  • Fixed an issue causing live mode to flood the logs when the backend crashed.

Release 5.2.1 (Day-One)

  • Fixed profile links with special characters in the data browser.
  • Fixed issue where topics with a single record were not being scanned.
  • Fixed JavaScript runtime memory leaks.
  • Fixed desktop download architecture detection: If you are running release 5.2.0 on Apple Silicon, please download mac-arm.zip instead of mac.zip through the UI.

Release 5.2.0

  • Introducing Apple Silicon & ARM support for Kadeck Desktop and Kadeck Teams.
  • Improved Kafka data streaming client and fixed offset calculation that was wrong in certain scenarios and prevented Kadeck from loading all records.
  • Schema Registry - dependent Protobuf codecs no longer get initialized without a configured Schema Registry
  • Fixed inclusion of codecs with negative priority in auto detection.
  • Data Policies: Added support for JSON paths as data protection fields (e.g., "accountid.string" will only affect "string" fields inside "accountid").
  • Data Policies: Specify groups that should be excluded from a data policy.
  • Data Catalog: Improves backwards compatibility for owner assignments in Data Catalog.