This is an automated email from the ASF dual-hosted git repository.
yuzelin pushed a change to branch release-1.4
in repository https://gitbox.apache.org/repos/asf/paimon.git
discard 1fe4cf22ae [python] Add conflict detection in shard update (#7630)
discard f27a002af4 [python] Fix duplicate _ROW_ID when file exceeds read batch
size (#7626)
new f975975992 [python] Fix duplicate _ROW_ID when file exceeds read batch
size (#7626)
new 411e31cdd4 [python] Add conflict detection in shard update (#7630)
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 (1fe4cf22ae)
\
N -- N -- N refs/heads/release-1.4 (411e31cdd4)
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 2 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:
paimon-python/pypaimon/tests/data_evolution_test.py | 1 -
1 file changed, 1 deletion(-)
