(pinot) branch xiangfu0/data-3221-10-physical-column-names updated (6345b17ab17 -> 1ba37041f04)

[xi...@apache.org]

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


 discard 6345b17ab17 Iterate column metadata directly during forward-index planning
 discard e0f7a92a761 DATA-3221 (12): make the new column-name accessor sorted and null-safe
 discard 3c83a4c8093 DATA-3221 (11): list physical columns without building the segment schema
 discard 82d4b5b4ead Adapt lazy loader and config test to column views
 discard 088d63a41ea Use existing column views instead of extra metadata APIs
 discard 1025203f334 DATA-3221 (10): publish the segment column arrays as one immutable pair
 discard 64f77154446 DATA-3221 (10): hold segment column metadata in sorted arrays, derive the map on demand
 discard 14df55d0a52 Keep focused packed metadata coverage
 discard 4c8cdd9e0d3 DATA-3221 (8+9 follow-up): drop the shared shape, pack bitsPerElement instead
 discard ece0ddd0a2d DATA-3221 (8+9): shared column shape and primitive min/max in ColumnMetadataImpl
 discard b5e770c1c50 Use per-segment schema state in lazy metadata tests
 discard 40d9a0b1317 Slim ColumnMetadataImpl to 72 bytes and derive the per-segment Schema lazily
 discard c633d4d078d Retain compact index configs for segment-specific loads
 discard 460d1c123c6 Reuse resolved index configs for lazy column materialization
 discard 28611868565 Materialize immutable-segment columns lazily behind an opt-in instance config (default off)
 discard 66306c77cc0 Use ordered index ids and keep focused container coverage
 discard f71886b640d Fold PhysicalColumnIndexContainer's IndexTypeMap into a presence mask plus dense readers
    omit ce3f3fe9c15 Trim duplicate data source metadata adapter tests
    omit eaba6c92070 Delegate immutable DataSourceMetadata to ColumnMetadata instead of snapshotting it
     add 8c879267bd9 Delegate immutable DataSourceMetadata to ColumnMetadata instead of snapshotting it (#19474)
     add 33ba69ab7f6 Fold PhysicalColumnIndexContainer's IndexTypeMap into a presence mask plus dense readers
     add 1a1847a79e4 Use ordered index ids and keep focused container coverage
     add a802950ff7e Materialize immutable-segment columns lazily behind an opt-in instance config (default off)
     add d00c2738a5e Reuse resolved index configs for lazy column materialization
     add 0133ad90ce6 Retain compact index configs for segment-specific loads
     add 3754ce93f55 Slim ColumnMetadataImpl to 72 bytes and derive the per-segment Schema lazily
     add e76a4f259a9 Use per-segment schema state in lazy metadata tests
     add 0073673fd99 DATA-3221 (8+9): shared column shape and primitive min/max in ColumnMetadataImpl
     add 4d394f464f4 DATA-3221 (8+9 follow-up): drop the shared shape, pack bitsPerElement instead
     add 702a6348a98 Keep focused packed metadata coverage
     add 7f2f9a6fb55 DATA-3221 (10): hold segment column metadata in sorted arrays, derive the map on demand
     add 3a39001a192 DATA-3221 (10): publish the segment column arrays as one immutable pair
     add 6393783dfe9 Use existing column views instead of extra metadata APIs
     add f23d03c0ac4 Adapt lazy loader and config test to column views
     add 8f189dca536 DATA-3221 (11): list physical columns without building the segment schema
     add 5ca4be2f53d DATA-3221 (12): make the new column-name accessor sorted and null-safe
     add 1ba37041f04 Iterate column metadata directly during forward-index planning

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   (6345b17ab17)
            \
             N -- N -- N   refs/heads/xiangfu0/data-3221-10-physical-column-names (1ba37041f04)

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:


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