Dear Flink / Pulsar Community, I am currently integrating Apache Flink with Apache Pulsar and noticed that the new Pulsar Source/Sink connector requires configuring an adminUrl in addition to the serviceUrl.
>From the Pulsar documentation, my understanding is that partitioned topics, >pattern subscriptions, and topic discovery can be handled entirely via the >Pulsar client API (broker endpoint) without requiring access to the HTTP Admin >API. However, when using the current Flink Pulsar connector, the adminUrl appears to be mandatory. In my environment, access to the Pulsar Admin endpoint is restricted, and I cannot obtain admin-level access. I would like to clarify: 1. Is the Admin URL strictly required by design in the current Flink Pulsar connector? 2. Are there configuration options to disable AdminClient usage if topic creation and metadata management are not needed? 3. Is there an officially supported way to use the connector in environments where the Pulsar Admin API is not accessible? I would appreciate confirmation on whether this is an intentional architectural requirement or if there are recommended alternatives for restricted environments. Thank you very much for your guidance! Best regards, Florian
