Sergio Peña
Sergio Peña
fix: disable SR ID_COMPATIBILITY_STRICT for Protobuf to allow serialization with external references
### Description Fixes https://github.com/confluentinc/ksql/issues/9169 The SR config `id.compatibility.strict` is set to `false` in this PR when serialization happens on streams that have a XXX_SCHEMA_ID reference. The `id.compatibility.strict` to true is...
The `ksqlDB Processing Log` documentation has lack details of how to configure the processing log log4j when Kafka requires authentication with either Kerberos and SSL (https://docs.ksqldb.io/en/latest/developer-guide/test-and-debug/processing-log/#log-stream). For instance, the following...
This issue is related to the `auto.register.schemas` config from SR. When I execute an INSERT statement, the row serializer attempts to register the stream/table schema in SR. First, If the...
Here's a list of changes I did on the parquet-benchmarks module: - Add variable to test PARQUET_1_0 format - Add variable to generate random data for the tests - Move...
**Describe the bug** When using the `additionalProperties` in a JSON_SR schema and the new JSON_SR converter is used for deserialization, the columns or fields of that schema are not correctly...
**Describe the bug** The `EXPLAIN` command displays an invalid statement which should be helpful to users to get more info about a stream or table. For instance, `DESCRIBE [EXTENDED] `...
**Describe the bug** A topic that has a `STRUCT` column cannot be deserialized from KSQL if `VARCHAR` is used in the KSQL schema. This issue is found only on `JSON_SR`...
When creating a JSON_SR stream, we should create the schema in the same order that is registered in SR. For example, I have this JSON schema in SR: ``` {...
**Describe the bug** When a query has errors, a list of errors collected is displayed by the `SHOW QUERIES EXTENDED` or `EXPLAIN ` commands. This list has a config to...
I have the following SR schema on subject `test-key` with all uppercase message names: ``` syntax = "proto3"; message M1_1 { int32 K1 = 1; } message M1_2 { int32...