- All Implemented Interfaces:
Filterand transposes them, pushing the aggregate below the filter.
In some cases, it is necessary to split the aggregate.
This rule does not directly improve performance. The aggregate will have to process more rows, to produce aggregated rows that will be thrown away. The rule might be beneficial if the predicate is very expensive to evaluate. The main use of the rule is to match a query that has a filter under an aggregate to an existing aggregate table.
Nested Class SummaryModifier and TypeClassDescription
static interfaceRule configuration.
Nested classes/interfaces inherited from class org.apache.calcite.plan.RelRule
RelRule.Done, RelRule.MatchHandler<R extends RelOptRule>, RelRule.OperandBuilder, RelRule.OperandDetailBuilder<R extends RelNode>, RelRule.OperandTransform
Methods inherited from class org.apache.calcite.plan.RelOptRule
any, convert, convert, convertList, convertOperand, convertOperand, equals, equals, getOperand, getOperands, getOutConvention, getOutTrait, hashCode, matches, none, operand, operand, operand, operand, operand, operandJ, operandJ, some, toString, unordered
(AggregateFilterTransposeRule.Config config)Creates an AggregateFilterTransposeRule.
AggregateFilterTransposeRule@Deprecated public AggregateFilterTransposeRule
(RelOptRuleOperand operand, RelBuilderFactory relBuilderFactory)Deprecated.
onMatchpublic void onMatch
(RelOptRuleCall call)Description copied from class:
RelOptRuleReceives notification about a rule match. At the time that this method is called,
call.relsholds the set of relational expressions which match the operands to the rule;
call.relsis the root expression.
Typically a rule would check that the nodes are valid matches, creates a new expression, then calls back
RelOptRuleCall.transformTo(org.apache.calcite.rel.RelNode, java.util.Map<org.apache.calcite.rel.RelNode, org.apache.calcite.rel.RelNode>, org.apache.calcite.plan.RelHintsPropagator)to register the expression.