hould be helpful. It provides good inputs for the
>>>> control
>>>> >>> flow framework design, to make the framework common enough to cover
>>>> the
>>>> >>> potential use cases.
>>>> >>>
>>>>
nd potential use
>>> cases
>>> >>>to be collected
>>> >>>2. Draft a FLIP with the scope of common control flow framework
>>> >>>3. We probably need a poc implementation to make sure the
>>> framework
>>&
>> >>>
>> >>>
>> >>> Thank you~
>> >>> Xintong Song
>> >>>
>> >>>
>> >>>
>> >>> On Tue, Jun 8, 2021 at 1:37 PM Yun Gao wrote:
>> >>>
>> >>>> Very than
>>>
> >>>> I also agree with the summarization by Xintong and Jing that control
> >>>> flow seems to be
> >>>> a common buidling block for many functionalities and dynamic
> >>>> configuration framework
> >>>> is a representative application that frequently requi
has pointed
>>>> out, it also required the control flow in cases like detection global
>>>> termination inside the iteration
>>>> (in this case we need to broadcast an event through the iteration
>>>> body to detect if there are still
>>>>
ith Xintong that the consistency guarantee
>>> would be a point to consider, we
>>> might consider if we need to ensure every operator could receive the
>>> dynamic configuration.
>>>
>>> Best,
>>> Yun
>>>
>>>
>>>
>
>
> Date:2021/06/08 11:52:12
> Recipient:JING ZHANGmailto:beyond1...@gmail.com>>
> Cc:刘建刚mailto:liujiangangp...@gmail.com>>; Xintong
> Song [via Apache Flink User Mailing List
> archive.] <mailto:ml%2bs2336050n44245...@n4.nabble.com>>; user <ma
on
> >>> framework, I also agree with Xintong that the consistency guarantee
> >>> would be a point to consider, we
> >>> might consider if we need to ensure every operator could receive the
> >>> dynamic configuration.
> >>>
> >
>>> Sender:kai wang<[hidden email]
>>> <http:///user/SendEmail.jtp?type=node&node=44278&i=2>>
>>> Date:2021/06/08 11:52:12
>>> Recipient:JING ZHANG<[hidden email]
>>> <http:///user/SendEmail.jtp?type=node&node=44278&i=3&
also agree with Xintong that the consistency guarantee would
>> be a point to consider, we
>> might consider if we need to ensure every operator could receive the
>> dynamic configuration.
>>
>> Best,
>> Yun
>>
>>
>>
>> ----------
>> Sender:kai wang
>> Da
operator could receive the
> dynamic configuration.
>
> Best,
> Yun
>
>
>
> --
> Sender:kai wang
> Date:2021/06/08 11:52:12
> Recipient:JING ZHANG
> Cc:刘建刚; Xintong Song [via Apache Flink User
>
nd start
the job. It may take a long time to recover. In some situations, stopping jobs
is intolerable, for example, the job is related to money or important
activities.So we need some technologies to control the running job without
stopping the job.
We propose to add control mode for flin
t;>>>
>>>> Steven Wu <[hidden email]
>>>> <http:///user/SendEmail.jtp?type=node&node=44245&i=1>> 于2021年6月4日周五
>>>> 下午11:11写道：
>>>>
>>>>> I am not sure if we should solve this problem in Flink. This is more
&g
852a
>>>>
>>>> On Fri, Jun 4, 2021 at 7:09 AM 刘建刚 <[hidden email]
>>>> <http:///user/SendEmail.jtp?type=node&node=44245&i=2>> wrote:
>>>>
>>>>> Hi everyone,
>>>>>
>>>>> Flink jobs are always
g:
>>>>
>>>>1.
>>>>
>>>> Change data processing’ logic, such as filter condition.
>>>>2.
>>>>
>>>>Send trigger events to make the progress forward.
>>>>3.
>>>>
>>>>
>>> be different as following:
>>>>
>>>>1.
>>>>
>>>>Change data processing’ logic, such as filter condition.
>>>> 2.
>>>>
>>>>Send trigger events to make the progress forward.
>>>&g
4.
>>>
>>>Change log level to debug current problem.
>>>
>>> The common way to do this is to stop the job, do modifications and
>>> start the job. It may take a long time to recover. In some situations,
>>> stopping jobs is intoler
d
>> start the job. It may take a long time to recover. In some situations,
>> stopping jobs is intolerable, for example, the job is related to money or
>> important activities.So we need some technologies to control the running
>> job without stopping the job.
>>
>>
t;>Change log level to debug current problem.
>>
>> The common way to do this is to stop the job, do modifications and
>> start the job. It may take a long time to recover. In some situations,
>> stopping jobs is intolerable, for example, the job is related to mon
some technologies to control the running
> job without stopping the job.
>
>
> We propose to add control mode for flink. A control mode based on the
> restful interface is first introduced. It works by these steps:
>
>
>1. The user can predefine some logic which supports
,
stopping jobs is intolerable, for example, the job is related to money or
important activities.So we need some technologies to control the running
job without stopping the job.
We propose to add control mode for flink. A control mode based on the
restful interface is first introduced. It works
21 matches
Mail list logo
