Bug report

In Debezium server, debezium-server-pulsar creates a topic under PulsarChangeConsumer.jaca. The topic has no tenant and namespace. In Pulsar, a topic without tenant/namespace implicitly defaults the public tenant and the default namespace.

This prevents debezium server sending messages to any other tenants but the default public tenant. This is a limitation to enable Debezium server to support multi-tenant Pulsar environment.

What Debezium connector do you use and what version?

This is from the latest Master branch.

What is the connector configuration?

n/a

What is the captured database version and mode of depoyment?

n/a

What behaviour do you expect?

To support non-default Pulsar tenant and namespace

What behaviour do you see?

Only the default tenant, public and the default namespace, default, are supported currently.

Do you see the same behaviour using the latest relesead Debezium version?

n/a

Do you have the connector logs, ideally from start till finish?

n/a

How to reproduce the issue using our tutorial deployment?

n/a

Feature request or enhancement

This is an enhancement

Which use case/requirement will be addressed by the proposed feature?

To support mutli-tenant and non-superuser token Pulsar deployment

Implementation ideas (optional)

Allow user to specify a tenant and namespace as an option.