Sorry for coming in so late.
This makes a lot of sense and I'd love to see it happen.
However, the avro glue registry relies heavily on flink-avro interfaces
which are currently not part of the public API.
I think we should sort this out first before externalizing this format.
To add on to that, since these interfaces directly expose Avro classes,
what's their API compatibility story?
No concerns for the json format though.
On 30/01/2023 09:04, yuxia wrote:
+1 (non-binding).
Thanks for driving it.
Best regards,
Yuxia
----- 原始邮件 -----
发件人: "Ahmed Hamdy" <hamdy10...@gmail.com>
收件人: "dev" <dev@flink.apache.org>
发送时间: 星期一, 2023年 1 月 30日 下午 4:01:14
主题: Re: [VOTE] Externalize AWS formats to flink-connector-aws
+1 (non-binding)
Thanks,
Ahmed
On Fri, 27 Jan 2023 at 17:24, Jing Ge <j...@ververica.com.invalid> wrote:
+1 Thanks for driving it!
Best regards,
Jing
On Fri, Jan 27, 2023 at 2:36 PM Danny Cranmer <dannycran...@apache.org>
wrote:
Hello Hong, thanks for driving this.
+1 on the proposal and the voting schema looks good.
Thanks
On Thu, Jan 26, 2023 at 5:15 PM Teoh, Hong <lian...@amazon.co.uk.invalid
wrote:
Hi all,
As discussed in the discussion thread [1], I would like to propose we
externalize flink-avro-glue-schema-registry and
flink-json-glue-schema-registry formats to the flink-connector-aws
repository [2].
Motivation:
1. We can unify and upgrade the AWS SDK versions more easily.
2. We can now move flink-connector-aws-base to the external repository
as
well.
Voting Schema:
Consensus, committers have binding votes, open for at least 72 hours.
Thanks,
Hong
[1] https://lists.apache.org/thread/03l99yz62mq3ngj8cvg8stk4foym65jq
[2] https://github.com/apache/flink-connector-aws/
