Replies: 1 comment 3 replies
-
Hi @ppilev , I refactored the stream configuration implementation here. The issue is not enough documented. A new method will expose But basically, in the 1.5 release, you could easily do this kind of thing var streamConfig = new StreamConfig();
streamConfig.AddConfig("application.id", "test-app");
streamConfig.AddConfig("metrics.interval.ms", 100000);
streamConfig.AddConfig("follow.metadata", true);
streamConfig.AddConfig("bootstrap.servers", "localhost:9092");
streamConfig.AddConfig("auto.offset.reset", AutoOffsetReset.Latest);
streamConfig.AddConfig("acks", Acks.Leader);
streamConfig.AddConfig("sasl.mechanism", SaslMechanism.ScramSha512); But your point still raise an error if you call something like that. I think I can adapt my PR to manage this kind of feature. streamConfig.AddConfig("auto.offset.reset", "Latest"); |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
hi @LGouellec,
I'm trying to initialize
StreamConfig
out of appsettings.json file usingIOptions<>
pattern, however becauseStreamConfig
is derived fromDictionary<string, dynamic>
the property setters ofStreamConfig
are ignored and the json configuration is directly translated to key-value pairs into the base class dictionary.Then I tried to modify my json config like
"auto.offset.reset": "Latest"
but I realized that this will just create an entry in the dictionary with a string value "Latest" and the type conversion won't be handled properly.Ultimately I'd like to be able to reuse existing configurations I have for
ClientConfig
,ConsumerConfig
andProducerConfig
and have them applied toStreamConfig
, however the internal implementation of the later completely prevents it.Do you see any way to workaround that issue?
Regards,
Beta Was this translation helpful? Give feedback.
All reactions