[iotdb] branch rocksdb/dev updated (d680373 -> ad3b863)

[ji...@apache.org]

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

jianyun pushed a change to branch rocksdb/dev
in repository https://gitbox.apache.org/repos/asf/iotdb.git.


 discard d680373  merge master URL: https://geelib.qihoo.net/geelib/repoMergeDetail?repoId=tsdb/iotdb&mergeId=11
     add c8a5c8f  [IOTDB-2787] Fix aligned mem chunk concurrent problem (#5322)
     add 8eab5ca  [IOTDB-2674] Multi-Raft Consensus Implementation based on Apache Ratis (#5255)
     add 05185a3  [IOTDB-2610] Add metrics for compation module (#5266)
     add 3cc07f7  [IOTDB-2726] Unify FragmentInstanceId interface (#5325)
     add bc3179b  [IoTDB-2260]Complete the basic version of DistributionPlanner (#5327)
     add 498f2a1  [IOTDB-2773] Fix overlapped data should be consumed first bug (#5329)
     add 8b528a8  [IoTDB-2260] Fix the compile error after merge PR 5327 (#5333)
     add 6644f52  [IOTDB-2727] add interface for mock testing (#5326)
     add 8710848  Fix the bug that FREQ does not support DOUBLE. (#5335)
     add cef081c  [IOTDB-2713] Analyze stage: define the schema fetcher interface (#5334)
     add 84a55e7  Fragment instance implement IConsensusRequest (#5336)
     add a9d7b17  [IOTDB-2798] Fix ConfigNode start process (#5340)
     add 06a360f  [IOTDB-2747] Start data node (#5330)
     add f9c582a  Merge branch 'master' into jianyun/dev
     add ad3b863  reolve merge conflicts

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   (d680373)
            \
             N -- N -- N   refs/heads/rocksdb/dev (ad3b863)

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: