This is an automated email from the ASF dual-hosted git repository.
martijnvisser pushed a change to branch
dependabot/maven/org.apache.commons-commons-compress-1.26.0
in repository https://gitbox.apache.org/repos/asf/flink-connector-kafka.git
discard 57a63919 [FLINK-35008] Address dependency convergence due to bumped
commons-compress
discard 84823602 [FLINK-35008] Bump org.apache.commons:commons-compress from
1.25.0 to 1.26.0
add 897001d5 [FLINK-35007] Add support for Flink 1.19 (#90)
add 2f5e3cf1 [hotfix] Add Java 21 as JDK to test for Flink 1.19.0 weekly
runs
add edba5a2b [FLINK-35008] Bump org.apache.commons:commons-compress from
1.25.0 to 1.26.1
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (57a63919)
\
N -- N -- N
refs/heads/dependabot/maven/org.apache.commons-commons-compress-1.26.0
(edba5a2b)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
No new revisions were added by this update.
Summary of changes:
.github/workflows/push_pr.yml | 4 +-
.github/workflows/weekly.yml | 12 +-
.../connectors/kafka/testutils/DataGenerators.java | 29 --
flink-python/dev/integration_test.sh | 18 ++
flink-python/pyflink/flink-conf.yaml | 311 +++++++++++++++++++++
pom.xml | 9 +-
6 files changed, 339 insertions(+), 44 deletions(-)
create mode 100644 flink-python/pyflink/flink-conf.yaml
