Hi Seb.
In my team we are migrating things to Kotlin because we find it much easier
to deal with. It's like the best of both worlds, but you do give up on
Flink Scala serializers, since the only way to get Kotlin Data Classes
working is by making them a POJO (or implementing your own TypeInfo).
luding that
> dependency. As far as we could tell it's not actually required.
>
> On 01/12/2021 19:56, Nicolás Ferrario wrote:
>
> Hi all, this would be awesome, I'm so tired of seeing Java 8 everywhere
> (reminds me of Python 2.7).
>
> We're currently building our code
Hi all, this would be awesome, I'm so tired of seeing Java 8 everywhere
(reminds me of Python 2.7).
We're currently building our code against Java 11 because that's the latest
version of Java available as a Flink Docker image, but it'd be great to use
newer versions. I think it would also help to
are using the following command to submit the job, I am afraid the
> dynamic properties could not take effect on the client side.
>
> /flink-1.14.0/bin/flink run-application ... -D
> kubernetes.certs.client.key.algo=EC
>
> Could you please export the enviro
nt first and have a try again?
>
> export KUBERNETES_CLIENT_KEY_ALGO_SYSTEM_PROPERTY=EC
>
> [1].
> https://github.com/fabric8io/kubernetes-client/blob/v5.5.0/kubernetes-client/src/main/java/io/fabric8/kubernetes/client/internal/CertUtils.java#L136
>
> Best,
> Yang
>
> Ni
Hi all, I am trying to run Flink on a K3s cluster and I'm getting this
exception:
io.fabric8.kubernetes.client.KubernetesClientException: An error has
> occurred.
>
> at
> io.fabric8.kubernetes.client.KubernetesClientException.launderThrowable(KubernetesClientException.java:64)
>
>
