nal
> information but this is definitely out of scope here.
> The autoscaler in general needs to have a good way to associate user code /
> operators with vertex ids for these types of use-cases that we need to
> investigate as a followup.
>
> Cheers
> Gyula
>
> On W
eed in external
>> information but this is definitely out of scope here.
>> The autoscaler in general needs to have a good way to associate user code /
>> operators with vertex ids for these types of use-cases that we need to
>> investigate as a followup.
>>
Hi everyone,
I'd like to start a vote on the FLIP-514: Custom Evaluator plugin for Flink
Autoscaler [1]. The discussion thread is here [2].
The vote will be open for at least 72 hours unless there is an objection or
insufficient votes.
[1]
https://cwiki.apache.org/confluence/display/FLINK/FLI
Hi everyone,
The vote[1] on FLIP-514[2] concluded with the following results:
Approving(+1) votes:
Gyula Fora (binding)
Rui Fan (binding)
Maximilian Michels (binding)
Őrhidi Mátyás (binding)
There were no disproving(-1) votes.
I'm happy to announce that FLIP-514 has been approved.
Thanks,
Pra
Hi All,
I would like to start a discussion of FLIP-514: Custom Evaluator plugin for
Flink Autoscaler [1].
Feel free to share your thoughts and suggestions to make this feature better.
[1]
https://cwiki.apache.org/confluence/display/FLINK/FLIP-514%3A+Custom+Evaluator+plugin+for+Flink+Autosc
gt;>
>>> On 29 Mar 2025, at 02:58, Venkatakrishnan Sowrirajan
>> wrote:
>>>
>>> Hi Pradeepta,
>>>
>>> Thanks for the nice proposal. I am curious, how does the current
>> autoscaler
>>> as well as the newly proposed custom ev
Thanks for the initiative. +1 and looking forward to its first release!
Thanks and Regards
Pradeepta
> On 21 May 2025, at 8:51 AM, Xintong Song wrote:
>
>
