; > I would suggest aiming to copy what the confluent DeSer libraries do
> > rather than having a schema id hard coded in the config.
> >
> > WDYT?
> > Kind regards, David.
> >
> > From: Kevin Lam
> > Date: Tuesday, 26 March 2024 at 20:06
> >
are compatible with the confluent
avro format.
WDYT?
Kind regards, David.
From: Anupam Aggarwal
Date: Saturday, 13 April 2024 at 16:08
To: dev@flink.apache.org
Subject: [EXTERNAL] Re: [DISCUSS] FLINK-34440 Support Debezium Protobuf
Confluent Format
Hi David,
Thank you for the suggestion
y what the confluent DeSer libraries do
> rather than having a schema id hard coded in the config.
>
> WDYT?
> Kind regards, David.
>
> From: Kevin Lam
> Date: Tuesday, 26 March 2024 at 20:06
> To: dev@flink.apache.org
> Subject: [EXTERNAL] Re: [DISCUSS] FLINK-
gt; > > I suggested an Apicurio registry format in the dev list, and
> > was
> > > > > > advised
> > > > > > > > to raise a FLIP for this, I suggest the same would apply here
> > (or
> > > > the
> > > > > > >
gt; > > > > > back to open source.
> > > > > > > > If you already have an implementation, let's decide which one
> > to
> > > > use
> > > > > :)
> > > > > > > >
> > > > > > > > Best,
> > > > > >
in the dev list, and
> > was
> > > > > > advised
> > > > > > > > to raise a FLIP for this, I suggest the same would apply here
> > (or
> > > > the
> > > > > > > > alternative to FLIPs if you cannot raise one
; Avro
> > > > > > > Apicurio format, prior to raising the Flip, and notice that
> the
> > > > > > readSchema
> > > > > > > in the SchemaCoder only takes a byte array ,but I need to pass
> > down
> > > > the
> > > >
gt; > I assume:
> > > > > >
> > > > > > * for the confluent Protobuf format you would extend the
> > Protobuf
> > > > > > format to drive some Schema Registry logic for Protobuf (similar
> to
> > > the
> > > > >
n be obtained and
> > the
> > > > > schema looked up using the Confluent Schema registry.
> > > > > * It would be good if any protobuf format enhancements for
> Schema
> > > > > registries pass down the Kafka headers (I am thinking as a
> > M
> > work with this.
> > > > * It would make sense to have the Confluent schema lookup in
> common
> > > > code, which is part of the SchemaCoder readSchema logic.
> > > > * I assume the ProtobufSchemaCoder readSchema would return a
> > Protob
schema lookup in common
> > > code, which is part of the SchemaCoder readSchema logic.
> > > * I assume the ProtobufSchemaCoder readSchema would return a
> Protobuf
> > > Schema object.
> > >
> > >
> > >
> > > I also wondered w
ats should be moved to the
> > Kafka connector repo, or whether they might in the future be used outside
> > Kafka – e.g. Avro/Protobuf files in a database.
> >Kind regards, David.
> >
> >
> > From: Kevin Lam
> > Date: Wednesday, 21 February 2024 at 18:51
>
day, 21 February 2024 at 18:51
> To: dev@flink.apache.org
> Subject: [EXTERNAL] [DISCUSS] FLINK-34440 Support Debezium Protobuf
> Confluent Format
> I would love to get some feedback from the community on this JIRA issue:
> https://issues.apache.org/jira/projects/FLINK/issues/FLINK-3
@flink.apache.org
Subject: [EXTERNAL] [DISCUSS] FLINK-34440 Support Debezium Protobuf Confluent
Format
I would love to get some feedback from the community on this JIRA issue:
https://issues.apache.org/jira/projects/FLINK/issues/FLINK-34440
I am looking into creating a PR and would appreciate some
I would love to get some feedback from the community on this JIRA issue:
https://issues.apache.org/jira/projects/FLINK/issues/FLINK-34440
I am looking into creating a PR and would appreciate some review on the
approach.
In terms of design I think we can mirror the `debezium-avro-confluent` and
15 matches
Mail list logo
