: Pierre Bedoucha
Kopi: user@flink.apache.org
Emne: Re: [Kubernetes Operator] NullPointerException from
KubernetesApplicationClusterEntrypoint
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
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
org.apache.flink.runtime.entrypoint.ClusterEntrypoint.shutDownAsync(ClusterEn
around the
Java one. You can access the origin via:
dataStream.javaStream.getTransformation()
I hope this helps.
Regards,
Timo
On 16.12.21 09:58, Pierre Bedoucha wrote:
> Hi Timo,
>
> And thank you for the detailed answer.
>
> We chose to go for the second alternative usin
Hi Timo,
And thank you for the detailed answer.
We chose to go for the second alternative using the following:
import org.apache.flink.streaming.api.transformations.OneInputTransformation
import
org.apache.flink.streaming.api.windowing.assigners.SlidingEventTimeWindows
val env = StreamExecutionE
Hi and thank you for this thread,
I'm also experimenting the same valid bug/limitation when connecting
streams.
I had a quick look in the annoucments but couldn't find any more
information: Would it be planned to propagate the Idle stream status to the
operator in the upcoming Flink minor versio
