This message was deleted.

If you don't set

dataabase.history.pulsar.service.url

, it will use the the client_auth_plugin and client_auth_params from the connector to connect.

Amazing, thanks for your help! I'm wondering how I could have figured this out on my own...I have read through the documentation from several different versions (3, 2.11, 2.10) and didn't see any example where

database.history.pulsar.service.url

wasn't set (and the documentation lists it as a

required

configuration).

// pass pulsar.client.builder if database.history.pulsar.service.url is not provided
        if (StringUtils.isEmpty(pulsarUrl)) {
            String pulsarClientBuilder = SerDeUtils.serialize(sourceContext.getPulsarClientBuilder());
            config.put(PulsarDatabaseHistory.CLIENT_BUILDER.name(), pulsarClientBuilder);
        }

I can see this block of code where this setting takes effect, but I didn't think to look there before your suggestion.

I think we fixed the issue but forgot to update the documentation. /cc @Neng @Anonymitaet

Thank you all! I've pre-analyzed the doc improvements and asked technical help from @Neng at https://github.com/apache/pulsar/issues/20501#issuecomment-1577758724. Will keep you updated on the progress.

1. yeah, it’s optional. 2. we should add such notes to clarify the behavior if not url set

@Neng Thanks for your quick response! Can you take a look at the question #3 and #4 in this issue?

@Anonymitaet how about changing the note to: “If it is not set, the

client_auth_plugin

and

client_auth_params

from the connector will be used to connect.” as there is no descriptions about

client_auth_plugin

and

client_auth_params

in debezium connector configuration section?

@Huanli Meng thank you. We discussed this issue last week and it has been fixed in https://github.com/apache/pulsar-site/pull/605