Congrats everyone :-)
Best
Yuan
On Fri, Jul 7, 2023 at 11:29 AM Hang Ruan wrote:
> Hi, Leonard.
>
> I would like to help to add this page. Please assign this issue to me.
> Thanks.
>
> Best,
> Hang
>
> Leonard Xu 于2023年7月7日周五 11:26写道：
>
>> Congrats to all !
>>
>> It will be helpful to promote
Thanks Yanfei for driving the release!
Best
Yuan
On Mon, Jan 30, 2023 at 8:46 PM Jing Ge via user
wrote:
> Hi Yanfei,
>
> Thanks for your effort. Looking forward to checking it.
>
> Best regards,
> Jing
>
> On Mon, Jan 30, 2023 at 1:42 PM Yanfei Lei wrote:
>
>> It is very happy to announce the
Hey Robin,
Thanks for sharing the detailed information. May I ask, when you are
saying "CPU usage is around 80% when checkpoints aren't running, and capped
at 100% when they are", do you see zigzag patterns of CPU usage, or is it
kept capped at 100% of CPU?
I think one possibility is that the sy
Hey Hjw,
Under the current Flink architecture (i.e., task states are stored locally
and periodically uploaded to remote durable storage during checkpointing),
there is no other way rather than scaling out your application to solve the
problem. This is equivalent to making the state size in each ta
That's definitely something we want to achieve in the future term, and your
input is very valuable.
One problem with the current queryable state setup is that the service is
bounded to the life cycle of Flink Job, which limits the usage of the state
store/service.
Thanks for your insights.
Best
Thanks, Xintong and Jark the great effort driving this, and everyone for
making this possible.
I've also Twittered this announcement on our Apache Flink Twitter account.
Best
Yuan
On Fri, Jun 3, 2022 at 12:54 AM Jing Ge wrote:
> Thanks everyone for your effort!
>
> Best regards,
> Jing
>
>
e/ReleaseNote.jspa?version=12349502&projectId=12315522
>
> We would like to thank all contributors of the Apache Flink community who
> made this release possible!
>
> Special thanks to Yuan Mei for managing the release and PMC members Robert
> Metzger, Chesnay Schepler and Piotr Nowojski.
>
> Regards,
> Roman
>
Hey Yidan,
KafkaShuffle is initially motivated to support shuffle data materialization
on Kafka, and started with a limited version supporting hash-partition
only. Watermark is maintained and forwarded as part of shuffle data. So you
are right, watermark storing/forwarding logic has nothing to do
ossible to be played twice after a recovery.
> Am I understanding this correctly?
>
> Thanks!
>
> On Mon, Jan 11, 2021 at 10:06 PM Yuan Mei wrote:
>
>> Hey Rex,
>>
>> You probably will find the link below helpful; it explains how
>> at-least-once (does not h
Hey Rex,
You probably will find the link below helpful; it explains how
at-least-once (does not have alignment) is different
from exactly-once(needs alignment). It also explains how the
alignment phase is skipped in the at-least-once mode.
https://ci.apache.org/projects/flink/flink-docs-release-1
Congrats!
On Thu, Aug 27, 2020 at 5:38 PM Xingbo Huang wrote:
> Congratulations Dian!
>
> Best,
> Xingbo
>
> jincheng sun 于2020年8月27日周四 下午5:24写道：
>
>> Hi all,
>>
>> On behalf of the Flink PMC, I'm happy to announce that Dian Fu is now
>> part of the Apache Flink Project Management Committee (PM
Congrats, Yu!
GXGX & well deserved!!
Best Regards,
Yuan
On Wed, Jun 17, 2020 at 9:15 AM jincheng sun
wrote:
> Hi all,
>
> On behalf of the Flink PMC, I'm happy to announce that Yu Li is now
> part of the Apache Flink Project Management Committee (PMC).
>
> Yu Li has been very active on Flink'
Congrats!
Best
Yuan
On Thu, Jan 16, 2020 at 5:59 PM jincheng sun
wrote:
> Hi everyone,
>
> I'm very happy to announce that Dian accepted the offer of the Flink PMC to
> become a committer of the Flink project.
>
> Dian Fu has been contributing to Flink for many years. Dian Fu played an
> essen
13 matches
Mail list logo
