KSQL should not silently overwrite Schemas in Registry with same name

[Rainer Schamm <ra...@lsd.co.za>]

Hi all

See existing issue:

https://github.com/confluentinc/ksql/issues/2427 <https://github.com/confluentinc/ksql/issues/2427>


Does anyone know if there is a work around for this? This problem is driving us crazy.
We really don't want to allow KSQL streams to constantly change the associated schema.

This is particularly painful for us because for some reason KSQL is not dealing correctly with date types.
We are creating the schema like this:

…
"type": {
        "type": "int",
        "connect.version": 1,
        "connect.name": "org.apache.kafka.connect.data.Date",
        "logicalType": "date"
      }
...

And KSQL is changing the type to this:

…
"type": {
        "type": „int"
      }
...

And then the sink connector fails to insert the int value because the db expects a date value.

Any help would be greatly appreciated.

Regards
Rainer