Zhu Zhu created FLINK-30815:
---
Summary: BatchTestBase/BatchAbstractTestBase are using Junit4
while some child tests are using JUnit5
Key: FLINK-30815
URL: https://issues.apache.org/jira/browse/FLINK-30815
Pr
Zhu Zhu created FLINK-30814:
---
Summary: The parallelism&maxParallelism of sort after a global
partitioning is forced to be 1
Key: FLINK-30814
URL: https://issues.apache.org/jira/browse/FLINK-30814
Project: F
I agree with JingGe and share same concern about sinkv2 may not stable enough
to be graduated.
After a quick browsing , I find some known bugs [1][2] that need to be fixed.
[1] https://issues.apache.org/jira/browse/FLINK-30238
[2] https://issues.apache.org/jira/browse/FLINK-29459
Best regards,
Yu
liuzhuo created FLINK-30813:
---
Summary: Residual zk data when using the kubernetes session mode
Key: FLINK-30813
URL: https://issues.apache.org/jira/browse/FLINK-30813
Project: Flink
Issue Type: Bug
Mate Czagany created FLINK-30812:
Summary: YARN with S3 resource storage fails for Hadoop 3.3.2
Key: FLINK-30812
URL: https://issues.apache.org/jira/browse/FLINK-30812
Project: Flink
Issue Ty
Thanks Xintong for initiating and sharing the discussion!
The agreement described in the summary looks pretty good. In particular, it
is great to know that ASF already has guidance requiring "voter must
provide with the veto a technical justification showing why the change is
bad". This is exactly
Hi all,
Thanks for all the comments. Sorry for my late reply.
I think I understand most of the suggestions. I still have the same
question about the adding task id/name like Jark.
And I have refactored the POC like this (
https://github.com/ruanhang1993/flink/commit/321192d17afbb9d00285a78a121676
Hi @John
Thanks for your feedback. I'd like to share my thoughts about your
questions and discuss them with you
> 10. Have you considered proposing a general consistency mechanism instead
of restricting it to TableStore+ETL graphs? For example, it seems to me to
be possible and valuable to define
Hi all,
IIUC, Chesnay means we should have a more general metric group for
**operator**
not for **coordinator** in JM, this would be useful to extend
other operator-specific
metrics in the future. That means the new scope format should be designed
for
the operator,
e.g., metrics.scope.jm-operator=
Shengkai Fang created FLINK-30811:
-
Summary: Fix sql gateway can not stop job correctly
Key: FLINK-30811
URL: https://issues.apache.org/jira/browse/FLINK-30811
Project: Flink
Issue Type: Bug
11 matches
Mail list logo