[QueryContext] Use QueryContext in functions #5613
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Replace
BrokerRequest
classes (AggregationInfo
,TransformExpressionTree
) with QueryContext classes (FunctionContext
,ExpressionContext
) for aggregation and transform functionsThis is the last PR of removing
BrokerRequest
classes from the query execution path. After this PR, the query engine will be independent ofBrokerRequest
and only accessQueryContext
classes, and all the redundant expression parsing will be saved.Besides replacing
BrokerRequest
classes, also refactoredDistinctCountThetaSketchAggregationFunction
to use theQueryContext
classes, which solves the TODO of standardizing the predicate strings and simplifies the predicate handling.Minor bug-fixes:
BaseBrokerRequestHandler
)DistinctCountRawThetaSketch
(InBrokerRequestToQueryContextConverter
)*
forCOUNT
when convertingFunctionCallAstNode
toFunctionContext
(InQueryContextConverterUtils
)Upgrade Notes
Because of the standardization of the
DistinctCountThetaSketch
predicate strings, please upgrade Broker before Server. The new Broker can handle both standard and non-standard predicate strings for backward-compatibility.