+1 (non-binding) A small suggestion: The message queue is currently used to store middle layer data of the streaming data warehouse. We hope use built-in dynamic table storage to store those middle layer. But those middle data of the streaming data warehouse are often provided to all business teams in a company. Some teams have not use Apache Flink as compute engine yet. In order to continue server those teams, the data in built-in dynamic table storage may be needed to copied to message queue again. If *the built-in storage could provide same consumer API as the commonly used message queues*, data copying may be avoided. So the built-in dynamic table storage may be promoted faster in the streaming data warehouse business.
Best regards, Jing Zhang Yufei Zhang <a...@apache.org> 于2021年11月11日周四 上午9:34写道： > Hi, > > +1 (non-binding) > > Very interesting design. I saw a lot of discussion on the generic > interface design, good to know it will address extensibility. > > Cheers, > Yufei > > > On 2021/11/10 02:51:55 Jingsong Li wrote: > > Hi everyone, > > > > Thanks for all the feedback so far. Based on the discussion[1] we seem > > to have consensus, so I would like to start a vote on FLIP-188 for > > which the FLIP has now also been updated[2]. > > > > The vote will last for at least 72 hours (Nov 13th 3:00 GMT) unless > > there is an objection or insufficient votes. > > > > [1] https://lists.apache.org/thread/tqyn1cro5ohl3c3fkjb1zvxbo03sofn7 > > [2] > https://cwiki.apache.org/confluence/display/FLINK/FLIP-188%3A+Introduce+Built-in+Dynamic+Table+Storage > > > > Best, > > Jingsong > > >
