[
https://issues.apache.org/jira/browse/FLINK-32938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zili Chen resolved FLINK-32938.
-------------------------------
Fix Version/s: pulsar-4.1.0
Resolution: Fixed
master via 78d00ea9e3e278d4ce2fbb0c8a8d380abef7b858
> flink-connector-pulsar should remove all `PulsarAdmin` calls
> ------------------------------------------------------------
>
> Key: FLINK-32938
> URL: https://issues.apache.org/jira/browse/FLINK-32938
> Project: Flink
> Issue Type: Improvement
> Components: Connectors / Pulsar
> Reporter: Neng Lu
> Assignee: Neng Lu
> Priority: Major
> Labels: pull-request-available
> Fix For: pulsar-4.1.0
>
>
> The flink-connector-pulsar should not access and interact with the admin
> endpoint. This could introduce potential security issues.
> In a production environment, a Pulsar cluster admin will not grant the
> permissions for the flink application to conduct any admin operations.
> Currently, the connector does various admin calls:
> ```{{{}{}}}{{{}{}}}
> PulsarAdmin.topics().getPartitionedTopicMetadata(topic)
> PulsarAdmin.namespaces().getTopics(namespace)
> PulsarAdmin.topics().getLastMessageId(topic)
> PulsarAdmin.topics().getMessageIdByTimestamp(topic, timestamp)
> PulsarAdmin.topics().getSubscriptions(topic)
> PulsarAdmin.topics().createSubscription(topic, subscription,
> MessageId.earliest)
> PulsarAdmin.topics().resetCursor(topic, subscription, initial, !include)
> ```
> We need to replace these calls with consumer or client calls.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
