Hi Xuannan,
sorry, for not entering the discussion earlier. Could you please update
the FLIP to how it would like after FLIP-84? I think your proposal makes
sense to me and aligns well with the other efforts from an API
perspective. However, here are some thought from my side:
It would be nice to already think about how we can support this feature
in a multi-statement SQL file. Would we use planner hints (as discussed
in FLIP-113) or rather introduce some custom DCL on top of views?
Actually, the semantics of a cached table are very similar to
materialized views. Maybe we should think about unifying these concepts?
CREATE MATERIALIZED VIEW x SELECT * FROM t;
table.materialize();
table.unmaterialize();
From a runtime perspecitive, even for streaming a user could define a
caching service that is backed by a regular table source/table sink.
Currently, people are busy with feature freeze of Flink 1.11. Maybe we
could postpone the discussion after May 15th. I guess this FLIP is
targeted for Flink 1.12 anyways.
Regards,
Timo
On 30.04.20 09:00, Xuannan Su wrote:
Hi all,
I'd like to start the vote for FLIP-36[1], which has been discussed in
thread[2].
The vote will be open for 72h, until May 3, 2020, 07:00 AM UTC, unless
there's an objection.
Best,
Xuannan
[1]
https://cwiki.apache.org/confluence/display/FLINK/FLIP-36%3A+Support+Interactive+Programming+in+Flink
[2]
http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/DISCUSS-FLIP-36-Support-Interactive-Programming-in-Flink-Table-API-td40592.html
