Thanks for the explanation, Piotr,
I agree that the completable future solution would work for single-threaded
readers. From API perspective, returning a completable future means the
reader must have an internal thread to complete that future. I was actually
thinking of some sources that are
+1. Thanks for putting the proposal together Shuyi.
DDL has been brought up in a couple of times previously [1,2]. Utilizing
DDL will definitely be a great extension to the current Flink SQL to
systematically support some of the previously brought up features such as
[3]. And it will also be
wangsan created FLINK-10770:
---
Summary: Some generated functions are not opened properly.
Key: FLINK-10770
URL: https://issues.apache.org/jira/browse/FLINK-10770
Project: Flink
Issue Type: Bug
Dear community,
the release-1.7 branch has been created [1]. This unblocks the master from
merging new features into it.
If you are working on a 1.7 relevant bug fix, then it is important to merge
it into the release-1.7 and master branch.
[1] https://github.com/apache/flink/tree/release-1.7
