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

xiangfu0 pushed a change to branch xiangfu0/codex/codec-runtime-buffers
in repository https://gitbox.apache.org/repos/asf/pinot.git


 discard 64edf321937 Use caller-owned buffers for codec pipelines
     add 2e9f31bdfed Add CombinePlanNode extension points for substituting 
combine operators (#19438)
     add 2c313412f1c Gate preprocess() on needPreprocess() in cold-download and 
consuming segment callers (#19394)
     add d08ac91365f Match the Spark ingestion plugin name to the directory it 
ships in (#19442)
     add fcdd8d6bcd2 Use caller-owned buffers for codec pipelines

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   (64edf321937)
            \
             N -- N -- N   refs/heads/xiangfu0/codex/codec-runtime-buffers 
(fcdd8d6bcd2)

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:
 .../apache/pinot/core/plan/CombinePlanNode.java    | 106 ++++++++++++++-------
 .../immutable/ImmutableSegmentLoader.java          |  21 +++-
 .../LaunchSparkDataIngestionJobCommand.java        |   7 +-
 .../LaunchSparkDataIngestionJobCommandTest.java    |  62 ++++++++++++
 4 files changed, 158 insertions(+), 38 deletions(-)
 create mode 100644 
pinot-tools/src/test/java/org/apache/pinot/tools/admin/command/LaunchSparkDataIngestionJobCommandTest.java


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

Reply via email to