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

healchow pushed a change to branch master
in repository https://gitbox.apache.org/repos/asf/inlong.git


    omit 084903ef5 [INLONG-7306][Sort] Use properties to save extended 
parameters in Redis LoadNode (#7307)
    omit efc116727 [INLONG-7292][Sort] S3DirtySink flushes too quickly (#7290)
    omit 95260e20a [INLONG-7286][Sort] Fix issue of tableidentifier being null 
when addRow (#7287)
    omit 3ce864721 [INLONG-7291][Sort] Fix bug of dirtysink not opening for 
jdbc multiple sink (#7288)
     new e8432ed88 [INLONG-7291][Sort] Fix bug of dirty sink not opening for 
jdbc multiple sink (#7288)
     new 093a10516 [INLONG-7286][Sort] Fix issue of tableIdentifier being null 
when addRow (#7287)
     new 86ed2fd23 [INLONG-7293][Sort] S3DirtySink flushes too quickly (#7290)
     new 674f5a759 [INLONG-7306][Sort] Use properties to save extended 
parameters in Redis LoadNode (#7307)

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   (084903ef5)
            \
             N -- N -- N   refs/heads/master (674f5a759)

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 4 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:

Reply via email to