Sorry, I read something wrong when I read FLIP.
It's fine for me.
Best,
Rui
On Thu, Nov 16, 2023 at 2:32 PM Junrui Lee wrote:
> Hi Rui,
>
> Thank you for your feedback. Regarding your question, I want to let you
> know that we have included the alternative getter method "@PublicEvolving
> Map
Hi Rui,
Thank you for your feedback. Regarding your question, I want to let you
know that we have included the alternative getter method "@PublicEvolving
Map getGlobalJobParameters()" in this FLIP. And this method
will provide users with global job parameters.
I would appreciate it if you could sh
Thanks Junrui for driving this proposal!
Overall looks good to me! I have a question:
How do the flink users to getGlobalJobParameters if
RuntimeContext#getExecutionConfig is removed?
Is there any alternative api? Or is this feature removed?
Maybe this is a noob question and I may have missed
som
Hi dear flink users and devs:
FLIP-364[1] intends to make some improvements to restart-strategy
and discuss updating some of the default values of exponential-delay,
and whether exponential-delay can be used as the default restart-strategy.
After discussing at dev mail list[2], we hope to collect
Thanks Junrui for creating the FLIP and kicking off this discussion.
Exposing a mutable ExecutionConfig which is even shared by multiple
operators is truly a defect which can result in weird results.
+1
Thanks,
Zhu
Junrui Lee 于2023年11月15日周三 16:53写道：
> Hi all,
>
> I'd like to start a discussio
Hi Jinzhong,
Sorry to answer you just now. We have switched from incremental checkpoint
to non-incremental checkpoint before, I think one of the reasons is the
difficulty to handle properly the clean up of checkpoints on S3. But with
the flink operator's periodic savepoint it may change. I'll re-
Thanks Maximilian and Gyula, I'll keep you updated.
Best,
Yang
On Sat, 11 Nov 2023 at 16:18, Maximilian Michels wrote:
> Hi Yang,
>
> We're always open to changes / additions to the autoscaler logic and
> metric collection. Preferably, we change these directly in the
> autoscaler implementation
Hi devs and users,
Yesterday was the first release sync of Flink 1.19, I’d like to share the
summary:
- Sync meeting
We switched back to google meet because there's some account limitation for
zoom on some region and the google meet is available when creator is not
online.
The meeting will happen
Hi all,
I'd like to start a discussion of FLIP-391: Deprecate
RuntimeContext#getExecutionConfig[1].
Currently, the FLINK RuntimeContext is important for connecting user
functions to the underlying runtime details. It provides users with
necessary runtime information during job execution.
However,
