chenyuzhi created FLINK-34576:
-
Summary: Flink deployment keep staying at RECONCILING/STABLE status
Key: FLINK-34576
URL: https://issues.apache.org/jira/browse/FLINK-34576
Project: Flink
Issue Ty
Hi Zakelly,
> 5. I'm not very sure ... revisiting this later since it is not important.
It seems that we still have some details to confirm about this
question. Let's postpone this to after the critical parts of the
design are settled.
> 8. Yes, we had considered ... metrics should be like after
Adrian Vasiliu created FLINK-34575:
--
Summary: Vulnerabilities in commons-compress 1.24.0; upgrade to
1.26.0 needed.
Key: FLINK-34575
URL: https://issues.apache.org/jira/browse/FLINK-34575
Project: Fl
Gabor Somogyi created FLINK-34574:
-
Summary: Add CPU and memory size autoscaler quota
Key: FLINK-34574
URL: https://issues.apache.org/jira/browse/FLINK-34574
Project: Flink
Issue Type: New Fe
Thanks Etienne for the pointers!
Very useful
Best,
Lorenzo
On Mar 4, 2024 at 11:53 +0100, Etienne Chauchot , wrote:
> Hi Lorenzo,
>
> There is a umbrella ticket [1] but it is intended to track the CI
> feature implementation and is now closed.
>
> I think the best is that each connector maintainer
LSZ created FLINK-34573:
---
Summary: the task is stuck on the high presure
Key: FLINK-34573
URL: https://issues.apache.org/jira/browse/FLINK-34573
Project: Flink
Issue Type: Bug
Components: Run
Hi Yunfeng,
For 1:
I had a discussion with Lincoln Lee, and I realize it is a common case the
same-key record should be blocked before the `processElement`. It is easier
for users to understand. Thus I will introduce a strict mode for this and
make it default. My rough idea is just like yours, by
He Wang created FLINK-34572:
---
Summary: JDBC: Support OceanBase catalog
Key: FLINK-34572
URL: https://issues.apache.org/jira/browse/FLINK-34572
Project: Flink
Issue Type: New Feature
Compo
Hi devs,
I'm happy to announce that FLIP-314: Support Customized Job Lineage
Listener [1] has been accepted with 9 approving votes (5 binding) [2]:
- Peter Huang (non-binding)
- Yangze Guo (binding)
- Zhanghao Chen (non-binding)
- Maciej Obuchowski (non-binding)
- Gyula Fóra (binding)
- Márton Ba
Hi all,
Thanks for sharing your opinions!
I'd like to draw a conclusion. I had an offline discussion with @Hangxiang
Yu and @Junrui Lee today, and we agreed that option 2 could make the
package cleaner, thus it is a better way to go.
We will follow option 2, and the deprecation will be discussed
Hi Lorenzo,
There is a umbrella ticket [1] but it is intended to track the CI
feature implementation and is now closed.
I think the best is that each connector maintainer does his own ticket.
Here is the one I did for Cassandra (there is an ongoing PR also): [2]
Best
Etienne
[1] https://i
Hi Zakelly,
Thanks for the responses!
> 1. I will discuss this with some expert SQL developers. ... mode for
> StreamRecord processing.
In DataStream API there should also be use cases when the order of
output is strictly required. I agree with it that SQL experts may help
provide more concrete
Thank you Etienne for the information.
Is there any Jira ticket about this?
Also an umbrella one?
Or connector maintainers will do on their own?
Thank you!
On Mar 4, 2024 at 10:23 +0100, Etienne Chauchot , wrote:
> Hi connector authors,
>
> I'd like to bring a piece of information about the CI o
Hi connector authors,
I'd like to bring a piece of information about the CI of connectors:
With the release of flink-connector-parent 1.1.0, you can now skip the
archunit tests for a particular CI build as described here [1].
Indeed, each connector needs to be tested against last 2 minor vers
14 matches
Mail list logo
