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

xiangfu0 pushed a change to branch xiangfu0/data-3221-10-physical-column-names
in repository https://gitbox.apache.org/repos/asf/pinot.git


    omit 779344d7920 Assert the preprocess check leaves the segment schema 
unbuilt on the server load path
    omit 455353d45a0 Iterate column metadata directly during forward-index 
planning
    omit 7bb43fcf844 DATA-3221 (12): make the new column-name accessor sorted 
and null-safe
    omit af1b79922c9 DATA-3221 (11): list physical columns without building the 
segment schema
     add ae1667b1327 Fix the column metadata mock in index loading tests
     add e25648b7409 DATA-3221 (11): list physical columns without building the 
segment schema
     add a26669b1042 DATA-3221 (12): make the new column-name accessor sorted 
and null-safe
     add d07e7ff815c Iterate column metadata directly during forward-index 
planning
     add cc4d67f14ee Assert the preprocess check leaves the segment schema 
unbuilt on the server load path

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   (779344d7920)
            \
             N -- N -- N   
refs/heads/xiangfu0/data-3221-10-physical-column-names (cc4d67f14ee)

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:
 .../segment/local/segment/index/loader/IndexLoadingConfigTest.java    | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to