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~
