getting the following error message.

ksql> CREATE STREAM CUSTOMERS_SRC WITH (KAFKA_TOPIC='asgard.public.customers', VALUE_FORMAT='AVRO'); Avro schema for message values on topic asgard.public.customers does not exist in the

It has been removed in favor of operator. Are there still docs from before on how to deploy the helm charts?

I am aware there have been a number of Community version related issues eg #85 and #219 but I was wondering how you would feel about a PR adding some more documentation and maybe configuration to this stack.

As a user I would love to have it documented specifically that I can utilize community-only things by setting certain parameters. Also exclude certain packages from the install stack.
And

I would like to set

SET 'auto.offset.reset'='earliest';
SET 'auto.offset.reset'='latest';

I hoped it would work like the following with the generic 'client.ksql' command:
client.ksql('SET 'auto.offset.reset'='earliest'');

It works well from KSQL CLI, so I think it is not a KSQL issue, but a limitation in the Python wrapper?

I found this related ticket:
https://github.com/bryany

Goals

• Fix error during DROP caused by the persistent queries dependencies needing prior termination for the STREAMS & TABLES instantiated with CREATE AS SELECT statement.
• Return useful information about the errors still occuring.

Problem obs

This is something I came up with recently and wanted to keep track as a possible upcoming feature to improve the resource definition and the state handling (see #2) at the same time.

I wont have the time to help implement that in the next weeks so I wanted to throw the idea and see were it goes from there 😉.

There is a lot of documentation to help figure out the rationale but it's mostl