Member since
09-10-2015
9
Posts
3
Kudos Received
3
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
1153 | 09-01-2017 07:33 AM | |
2234 | 05-24-2017 03:42 PM | |
3912 | 11-11-2016 09:55 AM |
05-30-2017
10:03 AM
I think that is not possible at the moment.
... View more
05-24-2017
03:42 PM
1 Kudo
From version 0.10.2.0 it is supported to use different keystores You need to set config: listener.name.<CLIENTNAME IN LOWERCASE>.ssl.keystore.location If this client does not defined kafka will fallback to the default config: ssl.keystore.location
... View more
11-11-2016
09:55 AM
2 Kudos
If the cluster is kerberized only one user can create new topic with command: bin/kafka-topics.sh --create --zookeeper <you zk node> --replication-factor 1 --partitions 1 --topic kafka_topic
This user is the user who runs the kafka broker, this is a zookeeper security limitation but there is a property in kafka auto.create.topics.enable, if this one is set to true the required topic will be created if the user produce/consume message. bin/kafka-console-producer.sh --broker-list broker address --topic kafka_topic --security-protocol SASL_PLAINTEXT
This command will create the kafka_topic, with different users.
... View more