Hi, thanks for the reply.
It looks like the container in the pod was restarting
kubernetes-jobmanager.sh kubernetes-application
State: Running
Started: Fri, 02 Dec 2022 22:20:09 +0700
Last State: Terminated
Reason: Error
Exit Code:239
We're investigating using internal SSL for our flink deployments, but I'm
curious how it handles cases where the certificates expire while a job is
running. We run a key distribution infrastructure with client/server keys
that expire fairly quickly (~days), so for example, long-running streaming
j
Yeah I took a look too...I guess that even if both work the clearer
(winner) option would be the Keyed(Co)ProcessFunction.
Anyway, thanks a lot!
Salva
On Fri, Dec 2, 2022, 12:23 Gen Luo wrote:
> Hi Salva,
>
> I mistook the idea, and yes both will work well.
> `stream.keyBy(...).process(new MyC
Hi Salva,
I mistook the idea, and yes both will work well.
`stream.keyBy(...).process(new MyCoProcessFunction());` uses
LegacyKeyedCoProcessOperator, and stream.keyBy(...).process(new
MyKeyedCoProcessFunction());` uses KeyedCoProcessOperator. Comparing the
two operators you'll find they are almos
Hi Gen,
Yeah but AFAIK keyed state is accessible as long as you are working with a
keyed state, so these two options:
```
stream.keyBy(...).process(new MyCoProcessFunction());`
stream.keyBy(...).process(new MyKeyedCoProcessFunction());`
```
will just work well with keyed state & timers if I'm no
