Hi Gyula,
Processing checkpoint halfway through `processElement` is problematic. The
current element will not be included in the input in-flight data, and we
cannot assume it has taken effect on the state by user code. So the best
way is to treat `processElement` as an 'atomic' operation. I guess
Hello Venkat,
There are few ways to get the JobID from the client side. JobID is alpha
numeric as 9eec4d17246b5ff965a43082818a3336.
When you submit the job using flink command line client , Job is returned
as
Job has been submitted with JobID 9eec4d17246b5ff965a43082818a3336
1. using below comma
The docker image is build for both linux/amd64 or linux/arm64/v8 platform.
The image you'll pull is based on the platform or the flag you set.
Regards.
On Fri, 15 Mar 2024, 2:01 am Yang LI, wrote:
> Dear Flink Community,
>
> Do you know if we have somewhere a tested ARM based flink docker image
Junrui,
Thanks for your answer for the above questions.
Allison and I work together on Flink. One of the main questions is, is
there an easy way to get the Flink "JobID" from the Flink client side?
Without the "JobID", users have no way to access Flink HistoryServer
other than searching through t
im using flink 1.81.1 api on java 11 and im trying to use a
BroadcastProcessFunction to filter a Products Datastream with a brand
autorized Datastream as broadcast.
So my first products Datastream contains different products that has a
field brand and my second brands Datastream contains only bran
Dear Flink Community,
Do you know if we have somewhere a tested ARM based flink docker image? I
think we can already run locally on an ARM macbook. But we don't have a
ARM specified docker image yet.
Regards,
Yang LI
Thank you for the detailed analysis Zakelly.
I think we should consider whether yield should process checkpoint barriers
because this puts quite a serious limitation on the unaligned checkpoints
in these cases.
Do you know what is the reason behind the current priority setting? Is
there a problem
Hi Gyula,
Well I tried your example in local mini-cluster, and it seems the source
can take checkpoints but it will block in the following AsyncWaitOperator.
IIUC, the unaligned checkpoint barrier should wait until the current
`processElement` finishes its execution. In your example, the element q
Hey all!
I encountered a strange and unexpected behaviour when trying to use
unaligned checkpoints with AsyncIO.
If the async operation queue is full and backpressures the pipeline
completely, then unaligned checkpoints cannot be completed. To me this
sounds counterintuitive because one of the be
