Kafka Protocol and Features

​

Supported Kafka Requests

The current implementation of the Apache Kafka protocol in StreamNative Cloud supports all the functionalities in Classic Engine and limited functionalities in the Ursa Engine. Specifically, the following Apache Kafka requests are currently supported:

Notes

• InitProducerId in Ursa Engine is partially supported when the transactional.id is NOT specified.

We’re actively working on adding support for more Kafka features and more Kafka requests to both Classic Engine and Ursa Engine. Please contact us for specific feature requests or if you notice any discrepancies.

​

Unsupported Kafka Requests

Because the Kafka protocol implementation in StreamNative Cloud is based on Pulsar for Classic Engine and Ursa for Ursa Engine, the following Kafka requests are irrelevant and not supports. For example, requests like:

​

Kafka metadata or storage related

These requests are irrelevant to StreamNative Cloud since data storage and replication are handled differently - either in BookKeeper or in the underlying object storage. Therefore, these requests are unlikely to be supported.

​

Security related

These security and ACL-related requests are not supported because StreamNative Cloud provides more comprehensive security mechanisms, including OAuth2 and Role-Based Access Control (RBAC). For information about using Kafka ACLs in StreamNative Cloud, see Manage Kafka ACLs to learn how to map Kafka ACLs to Pulsar ACLs.

​

Quotas related

Kafka’s quota feature is not supported. Please use Pulsar’s quota management instead.

​

API from latest KIPs

The API requests introduced from the latest KIPs are not yet supported. We are actively evaluating the feasibility of supporting them. If you have any specific feature requests, please contact us.

​

Supported topic configs

StreamNative Cloud supports the following topic configurations:

• cleanup.policy: This configuration can be set to either compact or compact,delete. The policy controls topic compaction and is only effective when compact is included in the setting. Due to StreamNative Cloud’s storage architecture, which preserves both raw and compacted segments rather than replacing individual log segments with compacted ones, we currently only support the values compact and compact,delete.

​

Supported Schema Registry APIs

StreamNative’s Kafka Schema Registry is compatible with Confluent Schema Registry.

Following are the supported APIs:

​

Schemas

GET /schemas/ids/{int: id}
GET /schemas/ids/{int: id}/subjects
GET /schemas/ids/{int: id}/schema
GET /schemas/ids/{int: id}/versions
GET /schemas/types

​

Subjects

GET /subjects
GET /subjects/(string: subject)/versions
GET /subjects/(string: subject)/versions/(versionId: version)
GET /subjects/(string: subject)/versions/(versionId: version)/schema
GET /subjects/(string: subject)/versions/(string: versionId)/referencedby
POST /subjects/(string: subject)
POST /subjects/(string: subject)/versions?normalize=(boolean: normalize)
DELETE /subjects/(string: subject)?permanent=(boolean: permanent)
DELETE /subjects/(string: subject)/versions/(string: versionId)

​

Mode

GET /mode

​

Compatibility

GET /compatibility/subjects/${subject}/versions/latest

​

Config

GET /config
GET /config/${subject}
PUT /config/${subject}