[jira] [Created] (FLINK-11002) Trigger.clear() will not be called after purged window

Yuan Yifan created FLINK-11002: -- Summary: Trigger.clear() will not be called after purged window Key: FLINK-11002 URL: https://issues.apache.org/jira/browse/FLINK-11002 Project: Flink Issue Type

回复：JIRA notifications

＋1 -- 发件人：Maximilian Michels 发送时间：2018年11月26日(星期一) 01:51 收件人：dev 主　题：Re: JIRA notifications It seems that some people find it useful to receive JIRA mails for new issues only. The "issues" mailing list gets all JIRA notifications,

Re: [DISCUSS] Support Interactive Programming in Flink Table API

Thanks for the explanation, Piotrek. Is there any extra thing user can do on a MaterializedTable that they cannot do on a Table? After users call *table.cache(), *users can just use that table and do anything that is supported on a Table, including SQL. Naming wise, either cache() or materialize(

Re: [DISCUSS] Table API Enhancement Outline

Yes，I agree the problem is needs attention. IMO. It depends on how we define the ‘w type. The way you above defines the 'w type as a tuple. If you serialize 'w to a Map, the compatibility will be better. Even more we can define ‘w as a special type. UDF and Sink can't be used directly. Must use 'w.

Re: JIRA notifications

It seems that some people find it useful to receive JIRA mails for new issues only. The "issues" mailing list gets all JIRA notifications, including updates to existing issues. So I'd leave things as they are now because JIRA doesn't allow individuals to configure receiving notifications only

Re: [DISCUSS] FLIP-27: Refactor Source Interface

Hi community, Glad to see this topic is still so active. Thanks for replying @Piotrek and @Becket. Last time, I expressed some rough ideas about the thread model. However I found that it's hard to describe clearly in mailing list. So I wrote it down with some graphs, exampled some kinds of models