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

xiangfu0 pushed a change to branch xiangfu0/codex/codec-stack/05-v7-format
in repository https://gitbox.apache.org/repos/asf/pinot.git


    omit 7a6cba4ae47 Add V7 raw forward index format for codec pipelines
    omit fcdd8d6bcd2 Use caller-owned buffers for codec pipelines
     add 84ad3cc2b9b Bump org.yaml:snakeyaml from 2.6 to 2.7 (#19445)
     add ca71554fc9d Bump com.puppycrawl.tools:checkstyle from 14.0.0 to 14.1.0 
(#19446)
     add 1ccc708ea1c Fix SSE dropping the FILTER clause of aggregations used 
only in HAVING or ORDER BY (#19437)
     add 77e091ce569 Use caller-owned buffers for codec pipelines
     add 5edd95c09a0 Add V7 raw forward index format 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   (7a6cba4ae47)
            \
             N -- N -- N   refs/heads/xiangfu0/codex/codec-stack/05-v7-format 
(5edd95c09a0)

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:
 .../core/query/request/context/QueryContext.java   | 16 +++--
 .../BrokerRequestToQueryContextConverterTest.java  |  9 +++
 .../pinot/queries/FilteredAggregationsTest.java    | 75 ++++++++++++++++++++++
 .../apache/pinot/spi/utils/CommonConstants.java    |  3 +
 pom.xml                                            |  4 +-
 5 files changed, 100 insertions(+), 7 deletions(-)


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

Reply via email to