Closed saubury closed 5 years ago
This should be fixed by https://github.com/confluentinc/ksql/pull/3147, right @agavra ?
yes it should be fixed by #3147
Thanks. Is there a work-around for the time being (other than down-grading)?
It appears that ksql.security.extension.class
is essentially mandatory in headless mode, and null
is not a legal value?
@agavra I believe you have a couple of workarounds you shared on other channels. Can you post them here and close this out?
For ksql.security.extension.class
a valid default is io.confluent.ksql.rest.server.security.KsqlDefaultSecurityExtension
. Setting this will cause the default partitions and replication factor setting to complain about null values as well. Any value (e.g. 4, 2) is valid as long as you have sufficient kafka brokers setup.
Thanks @agavra - that solution works well; thank-you!
KSQL server in headless mode (ie., using a
--queries-file
parameter forksql-server-start
) fails to start with fatal errorSteps to recreate
Create topic
Create queries file
Stop running (interactive) server
Start KSQL Server in headless mode
Server fails to start with error
Note - same issue occurs when using
ksql.queries.file=
setting withinksql-server.properties