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

jlli pushed a change to branch maintain-pool-selection-for-minimizeDataMovement
in repository https://gitbox.apache.org/repos/asf/pinot.git


    omit 993aa6b71c Enhance the minimizeDataMovement to keep the existing pool 
assignment
     add 95ed621750 Enhance the minimizeDataMovement to keep the existing pool 
assignment

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   (993aa6b71c)
            \
             N -- N -- N   
refs/heads/maintain-pool-selection-for-minimizeDataMovement (95ed621750)

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:
 .../helix/core/assignment/instance/InstanceTagPoolSelector.java         | 2 --
 1 file changed, 2 deletions(-)


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@pinot.apache.org
For additional commands, e-mail: commits-h...@pinot.apache.org

Reply via email to