[iotdb] branch jira5425 updated (93230e34d9 -> 43ab15e7b0)

[ta...@apache.org]

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

tanxinyu pushed a change to branch jira5425
in repository https://gitbox.apache.org/repos/asf/iotdb.git


    omit 93230e34d9 [IOTDB-5425] Consolidate all ConfigNodeClient to be managed by clientManager (#8891)
     add 4993c91c6d [To rel/1.0] Fix win CI (#8912)
     add 30464c5987 [To rel/1.0] Use gitbox thrift url instead of github to avoid download issue (#8914)
     add 534176f839 [To rel/1.0] [IOTDB-5431] Fix concurrent bug caused by using synchronizedSet() in DriverScheduler
     add 38adae4d7f [To rel/1.0] [IOTDB-5434] Fix occasional timeout error in CI
     add 43ab15e7b0 [IOTDB-5425] Consolidate all ConfigNodeClient to be managed by clientManager (#8891)

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   (93230e34d9)
            \
             N -- N -- N   refs/heads/jira5425 (43ab15e7b0)

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:
 .github/workflows/main-win.yml                     | 47 +------------
 pom.xml                                            |  8 +--
 .../execution/exchange/MPPDataExchangeManager.java | 78 +++++++++-------------
 .../db/mpp/execution/schedule/DriverScheduler.java | 23 ++++---
 4 files changed, 51 insertions(+), 105 deletions(-)