Thanks Arvid. As discussed offline, I have made the changes to doc.
1. Gotten rid of the protected methods in the constructor.
2. Added a new constructor that takes in BatchCreator/BufferWrapper from
the current one.
3. The new constructor defaults to the Default BatchCreator and
B
Ferenc Csaky created FLINK-37394:
Summary: Update CI Flink versions to 1.19 and 1.20 in Kudu
connector
Key: FLINK-37394
URL: https://issues.apache.org/jira/browse/FLINK-37394
Project: Flink
The vote for FLIP-491: BundledAggregateFunction for batched aggregation [1]
has concluded (discussion thread [2]). The vote will be closed [3].
There were 4 approving votes, all binding, and there were no disapprovals:
-Timo Walther (binding)
- Fabian Hüske (binding)
- Stefan Richter (binding)
-
Thank you both for the efforts. The progress sounds great.
JFYI, there are still a few other blocker issues, and based on the progress
of resolving them my estimation would be creating RC1 around next Friday.
So for this feature there's no need to rush. Take your time for code
reviewing and testin
Sry for the late reply, also +1 to have this in 2.0 given that we don't
guarantee backwards compatibility, and it is already not compatible in many
ways. Looking forward to this.
Best,
Zakelly
On Thu, Feb 27, 2025 at 9:20 AM Xintong Song wrote:
> Thank you both for the efforts. The progress so
The only reason to keep the old version of Kryo and not either upgrade or
remove Kryo is if there is a backward compatibility advantage. If backward
compatibility is breaking anyway, this seems an easy choice.
Java record support was the big motivation to this upgrade. From some simple
tests I'
A state migration tool that can migrate savepoints/checkpoints is a great idea
that would be very useful for a lot of scenarios. But that is a bigger scope
issue.
(fyi, CI is passing and PR should be fully ready)
Yanquan Lv created FLINK-37386:
--
Summary: Avoid sending too much CreateTableEvents when job
failover
Key: FLINK-37386
URL: https://issues.apache.org/jira/browse/FLINK-37386
Project: Flink
Issu
junzhong qin created FLINK-37392:
Summary: Kubernetes Operator UpgradeFailureException: HA metadata
not available to restore from last state
Key: FLINK-37392
URL: https://issues.apache.org/jira/browse/FLINK-37392
Dawid Wysakowicz created FLINK-37390:
Summary: Push filter into ChangelogNormalize
Key: FLINK-37390
URL: https://issues.apache.org/jira/browse/FLINK-37390
Project: Flink
Issue Type: Impro
Ferenc Csaky created FLINK-37389:
Summary: Add "flink-sql-connector-kudu" module
Key: FLINK-37389
URL: https://issues.apache.org/jira/browse/FLINK-37389
Project: Flink
Issue Type: Sub-task
Components: Flink CDC
Affects Versions: 3.0.0
Reporter: zexin gong
Attachments: screenshot-20250226-171451.png
If configured of schema.change.behavior: EVOLVE, an exception may be triggered
when reading binlog split: Field names must be unique. Found duplicates: [xxx
Sergey Nuyanzin created FLINK-37387:
---
Summary: License check behaves differently for different jdk
versions
Key: FLINK-37387
URL: https://issues.apache.org/jira/browse/FLINK-37387
Project: Flink
Hi devs,
Here's the summary of today's release sync.
- All documentation tickets have been closed.
- 27 out of 30 cross-team verification tickets have been closed. We are
targeting to complete them all by this weekend.
- There's 1 testability blocker, FLINK-35810, which we need help w
Thanks for bringing this to our attention! I would choose simplicity over
backward compatibility given Flink 2.0 offers the opportunity for breaking
changes. We will benefit from it from long-term's perspective. +1 for
upgrading Kryo in Flink 2.0 in a non compatible way.
Best regards,
Jing
On Wed
Thank you all for your feedback.
Let's leave this open for another day and unless there is any negative
feedback we can go ahead with merging the PR to bump the version for 2.0
Cheers
Gyula
On Wed, Feb 26, 2025 at 10:56 AM Jing Ge wrote:
> Thanks for bringing this to our attention! I would cho
Fabian Paul created FLINK-37391:
---
Summary: Change watchNamespace config in operator is not respected
while running
Key: FLINK-37391
URL: https://issues.apache.org/jira/browse/FLINK-37391
Project: Flink
Rafael Zimmermann created FLINK-37393:
-
Summary: Abnormally Long Checkpoint Duration After Full Checkpoint
Completion
Key: FLINK-37393
URL: https://issues.apache.org/jira/browse/FLINK-37393
Projec
Hi Xintong!
The PR is basically ready and CI almost passes (e2es work but there were
some minor checkstyle and related errors).
I will go through it and also test it manually a little today / tomorrow.
Unless something very unexpected comes up during the review and testing I
would expect to be ab
Hi Gyula,
Sorry for chime in late, just noticed the thread. And thanks for bringing
this up.
As one of the release managers, +1 for including this in Flink 2.0.
- Flink 2.0 does not guarantee state compatibility. We've mentioned that
in the 2.0-preview release announcement. In addition to
Hi Team,
Here is the summary on the outcomes from the PR review:
Externally added jars are resolved using the FlinkUserCodeClassLoader(child
classloader) in flink. This fix involved updating the class loader at the graph
execution level with the user code class loader which is expected as per na
zexin gong created FLINK-37395:
--
Summary: [BUG] When scan.startup.mode = latest-offset, an
NullPointerException will be triggered
Key: FLINK-37395
URL: https://issues.apache.org/jira/browse/FLINK-37395
P
22 matches
Mail list logo