This is an automated email from the ASF dual-hosted git repository.
biyan pushed a change to branch release-0.6
in repository https://gitbox.apache.org/repos/asf/incubator-paimon.git
discard 5534b45bf [spark] Fix call procedure compatibility with spark3.2
(#2707)
discard 5c04b45a8 [spark] Supports CTAS for different versions (#2591)
new ca245748c [spark] Supports CTAS for different versions (#2591)
new ec220f5a6 [spark] Fix call procedure compatibility with spark3.2
(#2707)
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 (5534b45bf)
\
N -- N -- N refs/heads/release-0.6 (ec220f5a6)
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:
.../src/test/scala/org/apache/spark/paimon/Utils.scala | 0
1 file changed, 0 insertions(+), 0 deletions(-)
copy paimon-spark/{paimon-spark-3.3 =>
paimon-spark-3.2}/src/test/scala/org/apache/spark/paimon/Utils.scala (100%)
