[This topic is pre-release documentation and is subject to change in future releases. Blank topics are included as placeholders.]

Factory for output processors. Output processors process the result set of a join or of a view and apply aggregation/grouping, having and some output limiting logic.

The instance produced by the factory depends on the presence of aggregation functions in the select list, the presence and nature of the group-by clause.

In case (1) and (2) there are no aggregation functions in the select clause.

Case (3) is without group-by and with aggregation functions and without non-aggregated properties in the select list:

 Copy imageCopy Code
select sum(volume)
. Always produces one row for new and old data, aggregates without grouping.

Case (4) is without group-by and with aggregation functions but with non-aggregated properties in the select list:

 Copy imageCopy Code
select price, sum(volume)
. Produces a row for each event, aggregates without grouping.

Case (5) is with group-by and with aggregation functions and all selected properties are grouped-by. in the select list:

 Copy imageCopy Code
select customerId, sum(volume) group by customerId
. Produces a old and new data row for each group changed, aggregates with grouping, see !:ResultSetProcessorRowGroup

Case (6) is with group-by and with aggregation functions and only some selected properties are grouped-by. in the select list:

 Copy imageCopy Code
select customerId, supplierId, sum(volume) group by customerId
. Produces row for each event, aggregates with grouping.

Namespace: net.esper.eql.core
Assembly:   NEsper (in NEsper.dll)

Syntax

Visual Basic (Declaration)
Public Class ResultSetProcessorFactory
C#
public class ResultSetProcessorFactory
Visual C++
public ref class ResultSetProcessorFactory

Inheritance Hierarchy

System.Object
  net.esper.eql.core.ResultSetProcessorFactory