Kafka

./bin/kafka-topics.sh --zookeeper localhost:2181 --delete --topic 'foobar'
Note: This will have no impact if delete.topic.enable is not set to true.
./bin/kafka-topics.sh --zookeeper localhost:2181 --list --topic '.*'

Refs

• https://www.confluent.io/blog/secure-kafka-deployment-best-practices/
• https://github.com/dpkp/kafka-python
• https://kafka.apache.org/quickstart

Using http to interface

• https://docs.confluent.io/3.0.0/kafka-rest/docs/intro.html#quickstart
• front with ngninx

Python Kafka

https://python.plainenglish.io/how-to-programmatically-create-topics-in-kafka-using-python-d8a22590ecde

Using kafka-python
from kafka.admin import KafkaAdminClient, NewTopic


admin_client = KafkaAdminClient(
    bootstrap_servers="localhost:9092", 
    client_id='test'
)

topic_list = []
topic_list.append(NewTopic(name="example_topic", num_partitions=1, replication_factor=1))
admin_client.create_topics(new_topics=topic_list, validate_only=False)
Using confluent_kafka
from confluent_kafka.admin import AdminClient, NewTopic


admin_client = AdminClient({
    "bootstrap.servers": "localhost:9092"
})

topic_list = []
topic_list.append(NewTopic("example_topic", 1, 1))
admin_client.create_topics(topic_list)

his is a known broker issue.
Topic deletions are asynchronous and depending on the cluster load and state it may take a long time for a topic to be completely removed from all brokers in the cluster.
It is therefore strongly recommended not to delete and re-create topics in this manner, but instead create new unique topics, or maintain (commit) the last read offset for the topic partitions to make sure no old messages are picked up by a consumer.