Uses of Class
org.apache.iotdb.db.query.executor.groupby.SlidingWindowGroupByExecutor
-
Packages that use SlidingWindowGroupByExecutor Package Description org.apache.iotdb.db.query.dataset.groupby org.apache.iotdb.db.query.executor.groupby org.apache.iotdb.db.query.executor.groupby.impl -
-
Uses of SlidingWindowGroupByExecutor in org.apache.iotdb.db.query.dataset.groupby
Fields in org.apache.iotdb.db.query.dataset.groupby declared as SlidingWindowGroupByExecutor Modifier and Type Field Description protected SlidingWindowGroupByExecutor[]GroupByTimeDataSet. slidingWindowGroupByExecutors -
Uses of SlidingWindowGroupByExecutor in org.apache.iotdb.db.query.executor.groupby
Methods in org.apache.iotdb.db.query.executor.groupby that return SlidingWindowGroupByExecutor Modifier and Type Method Description static SlidingWindowGroupByExecutorSlidingWindowGroupByExecutorFactory. getSlidingWindowGroupByExecutor(java.lang.String aggrFuncName, org.apache.iotdb.tsfile.file.metadata.enums.TSDataType dataType, boolean ascending) -
Uses of SlidingWindowGroupByExecutor in org.apache.iotdb.db.query.executor.groupby.impl
Subclasses of SlidingWindowGroupByExecutor in org.apache.iotdb.db.query.executor.groupby.impl Modifier and Type Class Description classEmptyQueueSlidingWindowGroupByExecutorWhen calculating MAX_TIME and LAST_VALUE (the MIN_TIME and FIRST_VALUE in descending order), the aggregation result always appears in the most recent pre-aggregation result.classMonotonicQueueSlidingWindowGroupByExecutorWhen computing MAX_VALUE, MIN_VALUE, EXTREME, we only add pre-aggregation results that maintain monotonicity to queue.classNormalQueueSlidingWindowGroupByExecutorWhen calculating MIN_TIME and FIRST_VALUE (MAX_TIME and LAST_VALUE in descending order), the aggregated result always appears at the head of the queue.classSmoothQueueSlidingWindowGroupByExecutorThe aggregation result is calculated from all pre-aggregation results in the currently maintained queue when calculating the COUNT, SUM, and AVG.
-