Almog Gavra

Just to clarify for people watching this ticket, ksqlDB supports working with topics that have a `.` in the name - you just need to declare the source name differently....

Hello @emrekuecuek - thanks for reporting this! ksqlDB currently does not support "keyless tables" (every table must have a named key field). @nateab and @mjsax have some ideas about how...

Adding some context here: my theory is that debezium always adds metadata columns at the end of the schema, so if you ever add anything to the schema, it'll be...

``` 2022-08-18T02:14:26.6175975Z org.apache.kafka.common.errors.SerializationException: Error deserializing Avro message for id -1 2022-08-18T02:14:26.6176584Z Caused by: org.apache.kafka.common.errors.SerializationException: Unknown magic byte! ``` This happens when trying to use the confluent schema registry to deserialize...

Hello @benjaminrhope - I believe this is a limitation where you need to have the `null` type be the first in the union of types (the default must be null...

You may want to look at windowed `GROUP BY` clauses: https://docs.ksqldb.io/en/latest/concepts/time-and-windows-in-ksqldb-queries/#windows-in-sql-queries this can help both of your questions. For the first, you can set the retention you want on windows....

Hello @maeh2k the fact that `INSERT INTO ... VALUES` is failing is expected (as outlined in the other issue you linked #5801) but that you cannot perform a JOIN is...

https://github.com/confluentinc/ksql/pull/2430 should address this issue

> To be correct, the CREATE OR REPLACE statement should cause a tombstone to be emitted. Though not sure how practical / obtainable this is, especially for none-materialized tables, I...

> Seems to be an incompatible query upgrade that we should reject until we can handle it correctly? I disagree here as well 😈 There's an argument that it's not...