Hi!
Seems like you still have an older version CRD installed for the
FlinkDeployment which doesn’t contain the newly introduced mode setting.
You can check
https://nightlies.apache.org/flink/flink-kubernetes-operator-docs-release-1.2/docs/operations/upgrade/
for the upgrade process.
Cheers
Gyula
I am following the operator quickstart
https://nightlies.apache.org/flink/flink-kubernetes-operator-docs-release-1.2/docs/try-flink-kubernetes-operator/quick-start/
kubectl create -f
https://raw.githubusercontent.com/apache/flink-kubernetes-operator/release-1.2/examples/basic.yaml
works fine, bu
Unsubscribe
Hello,
I found an SO thread that clarifies some details of window state size [1].
I would just like to confirm that this also applies when using a global
window with a custom trigger.
The reason I ask is that the TriggerResult API is meant to cover all
supported scenarios, so FIRE vs FIRE_AND_PUR
The Apache Flink community is very happy to announce the release of Apache
Flink Kubernetes Operator 1.2.0.
The Flink Kubernetes Operator allows users to manage their Apache Flink
applications and their lifecycle through native k8s tooling like kubectl.
Please check out the release blog post for
Is it possible to use the Flink Debezium format with the changelogs
generated by the Debezium MongoDB Connector? I have tried multiple
configurations (with and without json schema included), and I always
receive a java.io.IOException: Corrupt Debezium JSON message. Could it be
related to the fact t
