Thanks for the healthy discussion. Also +1 from my side for this FLIP.
Thanks,
Timo
On 24.11.21 19:05, Stephan Ewen wrote:
Thanks for all the details and explanation.
With the conclusion of the discussion, also +1 from my side for this FLIP
On Sat, Nov 13, 2021 at 12:23 PM Jingsong Li <jingsongl...@gmail.com> wrote:
Thanks Stephan and Timo, I have a rough look at your replies. They are
all valuable opinions. I will take time to discuss, explain and
improve them.
Hi Timo,
At least a final "I will start the vote soon. Last call for comments."
would have been nice.
I replied in the DISCUSS thread that we began to vote. If there are
supplementary comments or reply "pause voting first, I will reply
later", we can suspend or cancel the voting at any time.
I understand why the FLIP must take three days to vote, so that more
people can see it and put forward their opinions.
Best,
Jingsong
On Sat, Nov 13, 2021 at 1:27 AM Timo Walther <twal...@apache.org> wrote:
Hi everyone,
even though the DISCUSS thread was open for 2 weeks. I have the feeling
that the VOTE was initiated to quickly. At least a final "I will start
the vote soon. Last call for comments." would have been nice.
I also added some comments in the DISCUSS thread. Let's hope we can
resolve those soon.
Regards,
Timo
On 12.11.21 16:36, Stephan Ewen wrote:
Hi all!
I have a few questions on the design still, posted those in the
[DISCUSS]
thread.
It would be great to clarify those first before concluding this vote.
Thanks,
Stephan
On Fri, Nov 12, 2021 at 7:22 AM Jark Wu <imj...@gmail.com> wrote:
+1 (binding)
Thanks for the great work Jingsong!
Best,
Jark
On Thu, 11 Nov 2021 at 19:41, JING ZHANG <beyond1...@gmail.com>
wrote:
+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
--
Best, Jingsong Lee
