Hi Gyula, and thanks for your answer,
We tried without any cluster-id reference and still got the same error message.
It seems to be related with flink 1.16 as we have other jobs running with the
same flinkConfig and flink 1.15.
PB
Fra: Gyula Fóra
Dato: fredag, 31. mars 2023 kl. 14:41
Til:
Never seen this before but also you should not set the cluster-id in your
config as that should be controlled by the operator itself.
Gyula
On Fri, Mar 31, 2023 at 2:39 PM Pierre Bedoucha
wrote:
> Hi,
>
>
>
> We are trying to use Flink Kubernetes Operator 1.4.0 with Flink 1.16.
>
>
>
>
Hi,
We are trying to use Flink Kubernetes Operator 1.4.0 with Flink 1.16.
However, at the job-manager deployment step we get the following error:
```
Exception in thread "main" java.lang.NullPointerException
at
Hi,
FWIW, I asked a similar question here:
https://lists.apache.org/thread/1f01zo1lqcmhvosptpjlm6k3mgx0sv1m
:)
On Fri, Mar 31, 2023 at 3:57 AM Roberts, Ben (Senior Developer) via user <
user@flink.apache.org> wrote:
> Hi Gordon,
>
> Thanks for the reply!
> I think that makes sense.
>
> The
Hi Gordon,
Thanks for the reply!
I think that makes sense.
The reason for investigating is that generally we run our production workloads
across 2 kubernetes clusters (each in a different cloud region) for
availability reasons. So for instance requests to web apps are load balanced
between
https://github.com/EsotericSoftware/kryo/wiki/Migration-to-v5#migration-guide
Kroy themselves state that v5 likely can't read v2 data.
However, both versions can be on the classpath without classpath as v5
offers a versioned artifact that includes the version in the package.
It probably
Thanks for the update.
Martijn Visser 于2023年3月31日周五 14:35写道：
> Hi Tian,
>
> Thanks for flagging this. This is the first time that we've released a
> Flink version with connectors externalized and we're still discussing
> what's the best way to release connectors for new versions in a simple
Hi Tian,
Thanks for flagging this. This is the first time that we've released a
Flink version with connectors externalized and we're still discussing
what's the best way to release connectors for new versions in a simple way.
This is something that we're trying to get done asap.
Best regards,
