This is an automated email from the ASF dual-hosted git repository.
zhouyao2023 pushed a change to branch 2.3.4-release
in repository https://gitbox.apache.org/repos/asf/seatunnel.git
discard 94a5179350 [bugFix] mvn 'release:prepare' error (#6294)
discard 06d07afbba [Hotfix][CI][JDBC] Fix unstable e2e jdbc part 1 (#6292)
discard 4e688cc365 [Doc] Fix dead link with debezium (#6283)
discard 60a3cc6268 [Improve][Catalog] Use default tablepath when can not get
the tablepath from source config (#6276)
discard 1d2b65bfc8 Fix Jdbc sink target table name error (#6269)
discard 634d836864 [Release][2.3.4][release-note] Add release-note
add 2f62235e38 Fix Jdbc sink target table name error (#6269)
add f8158bb805 [Improve][Catalog] Use default tablepath when can not get
the tablepath from source config (#6276)
add 0e1236fc27 [Doc] Fix dead link with debezium (#6283)
add 349218dbdb [Hotfix][CI][JDBC] Fix unstable e2e jdbc part 1 (#6292)
add ef85b34d44 [bugFix] mvn 'release:prepare' error (#6294)
new f562f1def2 [Release][2.3.4][release-note] Add release-note
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 (94a5179350)
\
N -- N -- N refs/heads/2.3.4-release (f562f1def2)
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.
The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
