Sergio Peña

Reopene issue 'cause the fix only works for Protobuf

Seems this is fixed by the following PRs: https://github.com/confluentinc/ksql/pull/8933 https://github.com/confluentinc/ksql/pull/9047 https://github.com/confluentinc/ksql/pull/8984 When a user selects a schema ID that contains multiple Protobuf schema definitions, then the user must specify the...

There's a bug when using the VALUE_SCHEMA_ID and INSERT with Avro schemas. KSQL takes a different code path in Ksql when serializing the INSERT record when a SCHEMA_ID is found...

@rodesai The timeout is configurable through `ksql.streams.shutdown.timeout.ms`. The proposal is to derive the timeout from the # of threads and internal closures, thus deprecating and eliminating the ``ksql.streams.shutdown.timeout.ms` config?

I took a look at the timeouts that Kafka streams is using per stream thread. These are: - a producer has close(Long.MAX_VALUE) - two consumers have close(30 seconds hard-coded) -...

@rodesai is this still an issue? can I close the ticket and PR?

I will close this ticket. It's old. Re-open it if we need to work on this.

@mparikhcloudbeds I left a comment of a possible workaround here https://github.com/confluentinc/ksql/issues/8160#issuecomment-936728536. This workaround is based on the Avro [docs](https://avro.apache.org/docs/current/spec.html) about Schema Resolution that states that two schemas match if **both...

Thanks @nezihyigitbasi for the feedback. I fixed the issues you mentioned. You will be able to generate data this time.

Thanks @nezihyigitbasi I added the changes based on your feedback. I liked your explanation about random data, so I replaced the old paragraph with yours. I tried to figured out...