Re: [DISCUSS] Support Interactive Programming in Flink Table API
The design is quite interesting and useful.
I have several questions about your design:
1. Shall we add some persistence level hint to cache() function for
different temperature data? E.g. IN_MEM, IN_DISK, etc, or HOTTEST, HOT,
2. When will the corresponding cached data be cleaned, by some kind of GC?
Shall we add uncache() function to allow user manually delete the cached
3. Must the FlinkService be a running service or Flink will run the
service in TM?
Becket Qin <becket.qin@xxxxxxxxx> 于2018年11月20日周二 下午9:56写道：
> Hi all,
> As a few recent email threads have pointed out, it is a promising
> opportunity to enhance Flink Table API in various aspects, including
> functionality and ease of use among others. One of the scenarios where we
> feel Flink could improve is interactive programming. To explain the issues
> and facilitate the discussion on the solution, we put together the
> following document with our proposal.
> Feedback and comments are very welcome!
> Jiangjie (Becket) Qin