"persistent://tenant/ns/topic"
. StreamNative leverages Pulsar’s multi-tenancy feature and keeps the compatibility with the short topic names in Kafka.
For Kafka client users, they should follow the topic naming rule in this section. Otherwise, unexpected behaviors might happen.
You should specific topic names like:
topic
: it refers the topic persistent://public/default/topic
in the public/default
namespace.tenant.ns.topic
: it refers the topic persistent://tenant/ns/topic
in the tenant/ns
namespace.tenant.ns.xxx.yyy
: it refers the topic persistent://tenant/ns/xxx.yyy
in the tenant/ns
namespace.tenant/ns/topic
rather than tenant.ns.topic
to access topic topic
in namespace tenant/ns
.tenant1/ns1
and tenant2/ns2
), you can use Pulsar admin CLI to update the configuration dynamically:
kopAllowedNamespaces
config to the role you have. See Kafka ACLs on StreamNative Cloud for more details.
Take the command above for example and assume the role is user
, you need to run the following commands to grant the permissions:
kopAllowedNamespaces
config when you created a topic used by Kafka clients in a new namespace. For now, you need to execute the pulsar-admin brokers
command manually to update this config. In future, this step will be done automatically in the cloud console.