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 3fa3a3b3177 Assert the preprocess check leaves the segment schema 
unbuilt on the server load path
    omit afb3284206c Iterate column metadata directly during forward-index 
planning
    omit b5a27dd4524 DATA-3221 (12): make the new column-name accessor sorted 
and null-safe
    omit 17586a42d41 DATA-3221 (11): list physical columns without building the 
segment schema
     add 358b9b6e308 Stub column names in segment metadata test fixtures
     add cc45d66b674 DATA-3221 (11): list physical columns without building the 
segment schema
     add 7b726bd4674 DATA-3221 (12): make the new column-name accessor sorted 
and null-safe
     add a6d27f30c33 Iterate column metadata directly during forward-index 
planning
     add 9e0e5a1d5d9 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   (3fa3a3b3177)
            \
             N -- N -- N   
refs/heads/xiangfu0/data-3221-10-physical-column-names (9e0e5a1d5d9)

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:
 .../org/apache/pinot/controller/utils/SegmentMetadataMockUtils.java     | 2 ++
 1 file changed, 2 insertions(+)


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

Reply via email to