Please refer to https://flink.apache.org/community/ and send the email to
user-unsubscr...@flink.apache.org
Best,
Jane
On Fri, Feb 24, 2023 at 3:17 PM zhangjunjie wrote:
> 退订
>
>
>
退订
Hi Gen,
Thanks for your explanation.
Back to this code snippet, since they are not marked with "transient"
now, I suppose Flink will use avro to serialize them (null values). Is
there any benchmark to show the performance test between null values
serialization and "transient"? I mean, it is i
Hey!
You are right, these fields could have been of the PodTemplate /
PodTemplateSpec type (probably PodTemplateSpec is actually better).
I think the reason why we used it is two fold:
- Simple oversight :)
- Flink itself "expects" the podtemplate in this form for the native
integration as you c
Hi,
ValueState is a handle rather than an actual value. So it should never be
serialized. In fact, ValueState itself is not a Serializable. It should be
ok to always mark it as transient.
In this case, I suppose it works because the ValueState is not set (which
happens during the runtime) when th
Hi,
When I am reading the code from flink-training-repo [1], I noticed the
following code:
```java
public static class EnrichmentFunction
extends RichCoFlatMapFunction {
private ValueStaterideState; private
ValueStatefareState; ... }
```
From my understanding, since ValueState
Hi all,
Why does the FlinkDeployment CRD refer to the Pod class instead of the
PodTemplate class from the fabric8 library? As far as I can tell, the only
difference is that the Pod class exposes the PodStatus, which doesn't seem
mutable. Thanks in advance!
Best,
Mason
Hello
I was reviewing the HPA example at:
https://github.com/apache/flink-kubernetes-operator/blob/main/examples/hpa/basic-hpa.yaml
and I am a bit confused as to which spec this applies to.
Practically, I would assume that it's for scaling TaskManager worker pods.
Is that correct?
Then how does
The Apache Flink community is very happy to announce the release of Apache
Flink Kubernetes Operator 1.4.0.
The Flink Kubernetes Operator allows users to manage their Apache Flink
applications and their lifecycle through native k8s tooling like kubectl.
Release highlights:
- Flink Job Autosca
Ah I see, I'll have a look, thanks.
Am Do., 23. Feb. 2023 um 14:21 Uhr schrieb Gyula Fóra :
> If you are interested in helping to review this, here is the relevant
> ticket and the PR I just opened:
>
> https://issues.apache.org/jira/browse/FLINK-30786
> https://github.com/apache/flink-kubernetes
If you are interested in helping to review this, here is the relevant
ticket and the PR I just opened:
https://issues.apache.org/jira/browse/FLINK-30786
https://github.com/apache/flink-kubernetes-operator/pull/535
Cheers,
Gyula
On Thu, Feb 23, 2023 at 2:10 PM Gyula Fóra wrote:
> Hi!
>
> The cu
Hi!
The current array merging strategy in the operator is basically an
overwrite by position yes.
I actually have a pending improvement to make this configurable and allow
merging arrays by "name" attribute. This is generally more practical for
such cases.
Cheers,
Gyula
On Thu, Feb 23, 2023 at 1
Hello,
I noticed that if I set environment variables in both spec.podTemplate &
spec.jobManager.podTemplate for the same container (flink-maincontainer),
the values from the latter selectively overwrite the values from the
former. For example, if I define something like this (omitting metadata
pro
13 matches
Mail list logo
