Good idea @Yunze
Since `isSchemaValidationEnforced` is only on broker side, I decide to
support it on namespace and topic level.
Regards
Jiwei Guo (Tboy)
On Tue, May 17, 2022 at 11:24 AM Yunze Xu
wrote:
> For case 1, if you are using bytes schema to produce messages, it will be
> user's respo
For case 1, if you are using bytes schema to produce messages, it will be
user's responsibility to ensure the schema compatibility. Then at consumer side,
`Message#getValue`, which decodes the bytes internally via the schema,
should throw a `SchemaSerializationException` if the bytes of the value c
Il Mar 8 Mar 2022, 06:24 PengHui Li ha scritto:
> +1 the byte schema should also abide by the schema compatibility strategy
> If I remember correctly, the byte schema should always compatible with
> string schema
>
> Penghui
>
>
> On Tue, Mar 8, 2022 at 10:56 AM guo jiwei wrote:
>
> > Hi,
> >
+1 the byte schema should also abide by the schema compatibility strategy
If I remember correctly, the byte schema should always compatible with
string schema
Penghui
On Tue, Mar 8, 2022 at 10:56 AM guo jiwei wrote:
> Hi,
>I want to discuss the compatibility issue with the byte schema here
Hi,
I want to discuss the compatibility issue with the byte schema here.
For now, the byte-schema is compatible with all other schemas. This may
introduce more issues.
Case 1:
1. Consumer1 init with JSON schema for topic A.
2. But producer1 init without schema and send
