Weird Flink SQL error

Hi. I'm hitting an obfuscated Flink SQL parser error. Is there a way to get better errors for Flink SQL? I'm hitting it when I wrap some of the fields on an inner Row. *Works* CREATE TEMPORARY VIEW `test_content_metrics_view` AS SELECT DATE_FORMAT(TUMBLE_ROWTIME(rowtime, INTERVAL '1' DAY)

Re:Re: Flink Operator in an off-line k8s enviroment

Hi Geng Biao, I works for me, thank you. At 2022-11-22 23:16:41, "Geng Biao" wrote: Hi Mark, I guess you have to create your own local image registry service which your k8s cluster can connect to and upload the image of flink k8s operator to the service. After that, you

Fwd: Stand alone K8s HA mode with Static Tokens Used by Service Accounts

Hi team, Bumping this up again, from the AWS docs, the suggested approach is to simply upgrade the K8s java SDK client ( https://github.com/kubernetes-client/java/) being used. However, in Flink's case with the io.fabric8 K8s client, I am not sure how to handle it. Any help and guidance would be m

RE: "Authentication failed" in "ConnectionState" when enabling internal SSL on Yarn with self signed certificate

Last update : My flink version is 1.14.3 in fact. The application works when enabling internal SSL in “local” intra-jvm cluster mode, so the certificate seems correct. I see no log in Yarn server side, only that the application get killed. I will try to take stack traces… De : LINZ, Arnaud Envoy

RE: "Authentication failed" in "ConnectionState" when enabling internal SSL on Yarn with self signed certificate

Update : In fact this « Authentication failed” message also appears when SSL is turned off (and when the yarn application succeeds), so it’s more of a warning and has no link with the “freeze” when SSL is turned on. Thus, when internal SSL is enabled, I have no error in the yarn log, and the on

"Authentication failed" in "ConnectionState" when enabling internal SSL on Yarn with self signed certificate

Hello, I use Flink 1.11.2 in Yarn cluster mode. I’ve followed the instructions listed here (https://nightlies.apache.org/flink/flink-docs-master/docs/deployment/security/security-ssl/ ) to turn on

Re: Flink Operator in an off-line k8s enviroment

Hi Mark, I guess you have to create your own local image registry service which your k8s cluster can connect to and upload the image of flink k8s operator to the service. After that, you can run something like `helm install flink-kubernetes-operator flink-operator-repo/flink-kubernetes-operator

Re: Any way to improve list state get performance

Hi Tao, I think you just need an extra `isEmpty` VARIABLE and maintain it properly (e.g., when restoring the job, check if the list state is empty or not). Also, I remembered that the list state for rocksdb is not as performant as the map state when the state is large. Sometimes you could use a m

Flink Operator in an off-line k8s enviroment

Hi all, I installed flink operator following https://nightlies.apache.org/flink/flink-kubernetes-operator-docs-main/docs/ try-flink-kubernetes-operator/quick-start/. helm repo add flink-operator-repo https://downloads.apache.org/flink/flink-kubernetes-operator-1.2.0/ helm install flink-kubernete

Re: WIndowing in batch mode

Hi, This question has been posted on Stackoverflow, Slack and now the mailing list. Please don't spam the different channels for getting support on your question. This is a voluntary service, run by community members. Best regards, Martijn Visser On Tue, Nov 22, 2022 at 7:27 AM Suparn Lele (sul

Re: [Flink K8s operator] HA metadata not available to restore from last state

Hi Gyula :-) Okay, we're gonna upgrade to 1.15 and see what happens. Thanks a lot for the quick feedback and the detailed explanation! Best, Dongwon On Tue, Nov 22, 2022 at 5:57 PM Gyula Fóra wrote: > Hi Dongwon! > > This error mostly occurs when using Flink 1.14 and the Flink cluster goes

Re: [Flink K8s operator] HA metadata not available to restore from last state

Hi Dongwon! This error mostly occurs when using Flink 1.14 and the Flink cluster goes into a terminal state. If a Flink job is FAILED/FINISHED (such as it exhausted the retry strategy), in Flink 1.14 the cluster shuts itself down and removes the HA metadata. In these cases the operator will only

[Flink K8s operator] HA metadata not available to restore from last state

Hi, While using a last-state upgrade mode on flink-k8s-operator-1.2.0 and flink-1.14.3, we're occasionally facing the following error: Status: > Cluster Info: > Flink - Revision: 98997ea @ 2022-01-08T23:23:54+01:00 > Flink - Version: 1.14.3 > Error: