Hi, I would welcome any contribution that gets the HybridSource to become available for Table API and SQL use cases. I don't think there's anyone working on this right now.
I do think it requires a FLIP so that we can think how such a connector could be made available. Do you want to work on that Ran? Best regards, Martijn Visser https://twitter.com/MartijnVisser82 https://github.com/MartijnVisser On Sat, 7 May 2022 at 07:02, Jacky Lau <liuyong...@gmail.com> wrote: > I am interested in this, can you share your DDL first? At the same time, > there is no standard to describe hybrid Source DDL. > I also hope that the community can discuss together and share their ideas. > > Ran Tao <chucheng...@gmail.com> 于2022年5月7日周六 11:59写道： > > > HybridSource is a good feature, but now release version did not support > > table & sql api, i wonder which time it will be ready to end-users. > > > > And i have implemented a inner version of my company and it works well > now. > > the implementation of table & sql api may involve some core questions, > e.g. > > bounded & unbounded source start and end offset. child sources's schema > is > > different from hybrid source ddl schema (batch or streaming is more > fields > > or lack of some fields) we need process inconsistent filed problem or > > default filed value problem (in some child source lack of some fields) > etc. > > so here we may need a field mapping. > > > > i have some ideas and implementations, if table & sql api work in > progress > > i'm glad to share or take part in developing. > > > > thanks~ > > >
