This is an automated email from the ASF dual-hosted git repository.

vhs pushed a change to branch variant-intro-shredded-avro-support
in repository https://gitbox.apache.org/repos/asf/hudi.git


    omit dbc778a31489 Fix merge test
    omit cd2f82627fc7 feat(schema): Add read + write support for shredded for 
AVRO
     add ccb1ff4688a0 feat(schema): Add read + write support for shredded for 
AVRO

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   (dbc778a31489)
            \
             N -- N -- N   refs/heads/variant-intro-shredded-avro-support 
(ccb1ff4688a0)

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:
 .../apache/spark/sql/HoodieInternalRowUtils.scala  | 37 ++++++++++++++++++++++
 .../sql/hudi/dml/schema/TestVariantDataType.scala  |  4 +--
 2 files changed, 38 insertions(+), 3 deletions(-)

Reply via email to