Hi all,
Thanks for your valuable feedback. Here are my thoughts.
To Jark
I agree with your suggestions, and I've updated the sheet accordingly.
To Lincoln
> For the `DynamicFilteringEvent`, tend to keep it 'internal' since it's a
> concreate implementation of `SourceEvent`(and other two impleme
yuan created FLINK-32712:
Summary: Enhance Flink ogg-json format
Key: FLINK-32712
URL: https://issues.apache.org/jira/browse/FLINK-32712
Project: Flink
Issue Type: Bug
Components: Formats (
+1(binding)
Thanks for driving this proposal, it will be useful for rescale.
I’m preparing the FLIP-334[1], it will decouple the autoscaler and
kubernetes. In the end, we hope all kind of flink jobs work well with
rescale and autoscaler.
[1]
https://cwiki.apache.org/confluence/pages/viewpage.act
Hi Jane,
Thanks for the clarification. Commonly speaking, it is a good idea to show
the clear information that a class is only used internally, i.e. please
don't rely on it. However, the rule of using @Internal in the community is
not clearly defined, at least it is not as clear as
@Public/@Public
+1 (non-binding)
- Compiled and tested the source code via mvn verify
- Verified the signatures
- Downloaded the image : docker pull
ghcr.io/apache/flink-kubernetes-operator:e7045a6
- Deployed helm chart to test cluster
- Ran example job
Best,
Rui Fan
On Thu, Jul 27, 2023 at 10:53 PM Gyula Fóra
