You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 4, 2021. It is now read-only.
Today, for the Kafka event source, when people specify the list of bootstrap servers or topics, they're comma separated lists. When these lists get long (e.g. I'm messing with a usecase with ~100 topics), I'm wondering if a real array wouldn't be easier for people to manage. And for consistency, I have the same question for the list of bootstrap servers.
Most popular configuration in Java Kafka application properties uses comma separated list: "bootstrap.servers: A list of host/port pairs to use for establishing the initial connection to the Kafka cluster. "
it should be easy to support both, but might look kind of funky. If the "normal" flow is to use a comma for some of these then ok. It just felt odd as I was playing with it - and I was adding over a 100 entries :-)
I was thinking about the case where the yaml is in git and if someone changes something the "diff" will just show the entire long line and it might be hard to detect what changed. As separate lines it becomes easier.
Problem
Today, for the Kafka event source, when people specify the list of bootstrap servers or topics, they're comma separated lists. When these lists get long (e.g. I'm messing with a usecase with ~100 topics), I'm wondering if a real array wouldn't be easier for people to manage. And for consistency, I have the same question for the list of bootstrap servers.
Persona:
Event consumer
The text was updated successfully, but these errors were encountered: