Open mikebin opened 3 years ago
I think it just has to do with the prefix of the config name. If you set it in the properties file, I believe ksql.streams.main.consumer.max.poll.records
would be correct, but when setting it on the CLI, you remove ksql
I believe, so I think it would be SET 'streams.main.consumer.max.poll.records'='300';
Removing the ksql
prefix doesn't seem to work either in the CLI:
ksql> SET 'streams.main.consumer.max.poll.records'='300';
Not recognizable as ksql, streams, consumer, or producer property: 'streams.main.consumer.max.poll.records'
Describe the bug It doesn't seem to be possible to configure settings for specific types of clients used internally with the Kafka Streams naming prefixes in ksqlDB.
It might be helpful to be able to configure settings at this fine-grained level in some cases.
To Reproduce Version: ksqlDB 6.2.0
Expected behavior Successfully update property for the main consumers used in the query by Kafka Streams internally.
Actual behaviour
Additional context Also tried
main.consumer.max.poll.records
andmain.max.poll.records
, same error.max.poll.records
works.