Sergio Peña

Thanks @nezihyigitbasi. I added the minor changes you mentioned. Once #226 is committed, I will merge the code to my branch, and check it is applied correctly.

@nezihyigitbasi @rdblue I updated the branch with the latest changes of master (includes #226). No more work to do here.

It's looking good Ferd. Here are some questions I have. - Should we use fall back for bloom filters in case the bloom is not good for the row group?...

Go ahead @winnie-chiu and work on it. It hasn't been taken.

@rayokota is this supported in SR? The `JsonSchemaConverter` is returning `null` field values when the schema is defined using `additionaProperties`. I looked in the SR code and seems this' case...

@sanjay-awatramani do you know if SR supports the `additionalProperties`? Here's the question https://github.com/confluentinc/ksql/issues/9584#issuecomment-1252969778

@xavsan That issue might be related to the version of ksql than the SR schema. Which version are you using? The above config was added in 0.28

@drinehim One option to make it work with the new JSON_SR converter is to specify the `metadata` fields explicitly in the SR schema. That way SR will be able to...

@drinehim I created a JSON_SR stream with a MAP (`(metadata map)`) and this is what registered in SR: ``` { "properties": { "METADATA": { "connect.index": 0, "oneOf": [ { "type":...

@drinehim Nice!. It is actually supported. The SR API builds a MAP when the `connect.type` is found. It uses `STRING` as the key and the `additionalProperties` as the value. See...