1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139
// Copyright Materialize, Inc. and contributors. All rights reserved.
//
// Use of this software is governed by the Business Source License
// included in the LICENSE file.
//
// As of the Change Date specified in that file, in accordance with
// the Business Source License, use of this software will be governed
// by the Apache License, Version 2.0.
//! TopK planning logic.
//!
//! We provide a plan ([TopKPlan]) encoding variants of the TopK operator, and provide
//! implementations specific to plan variants.
//!
//! The TopK variants can be distinguished as follows:
//! * A [MonotonicTop1Plan] maintains a single row per key and is suitable for monotonic inputs.
//! * A [MonotonicTopKPlan] maintains up to K rows per key and is suitable for monotonic inputs.
//! * A [BasicTopKPlan] maintains up to K rows per key and can handle retractions.
use expr::ColumnOrder;
use serde::{Deserialize, Serialize};
/// A plan encapsulating different variants to compute a TopK operation.
#[derive(Clone, Debug, Serialize, Deserialize)]
pub enum TopKPlan {
/// A plan for Top1 for monotonic inputs.
MonotonicTop1(MonotonicTop1Plan),
/// A plan for TopK for monotonic inputs.
MonotonicTopK(MonotonicTopKPlan),
/// A plan for generic TopK operations.
Basic(BasicTopKPlan),
}
impl TopKPlan {
/// Create a plan from the information provided. Here we decide on which of the TopK plan
/// variants to select.
///
/// * `group_key` - The columns serving as the group key.
/// * `order_key` - The columns specifying an ordering withing each group.
/// * `offset` - The number of rows to skip at the top. Provide 0 to reveal all rows.
/// * `limit` - An optional limit of how many rows should be revealed.
/// * `arity` - The number of columns in the input and output.
/// * `monotonic` - `true` if the input is monotonic.
pub(crate) fn create_from(
group_key: Vec<usize>,
order_key: Vec<ColumnOrder>,
offset: usize,
limit: Option<usize>,
arity: usize,
monotonic: bool,
) -> Self {
if monotonic && offset == 0 && limit == Some(1) {
TopKPlan::MonotonicTop1(MonotonicTop1Plan {
group_key,
order_key,
})
} else if monotonic && offset == 0 {
// For monotonic inputs, we are able to retract inputs that can no longer be produced
// as outputs. Any inputs beyond `offset + limit` will never again be produced as
// outputs, and can be removed. The simplest form of this is when `offset == 0` and
// these removeable records are those in the input not produced in the output.
// TODO: consider broadening this optimization to `offset > 0` by first filtering
// down to `offset = 0` and `limit = offset + limit`, followed by a finishing act
// of `offset` and `limit`, discarding only the records not produced in the intermediate
// stage.
TopKPlan::MonotonicTopK(MonotonicTopKPlan {
group_key,
order_key,
limit,
arity,
})
} else {
// A plan for all other inputs
TopKPlan::Basic(BasicTopKPlan {
group_key,
order_key,
offset,
limit,
arity,
})
}
}
}
/// A plan for monotonic TopKs with an offset of 0 and a limit of 1.
///
/// If the input to a TopK is monotonic (aka append-only aka no retractions) then we
/// don't have to worry about keeping every row we've seen around forever. Instead,
/// the reduce can incrementally compute a new answer by looking at just the old TopK
/// for a key and the incremental data.
///
/// This optimization generalizes to any TopK over a monotonic source, but we special
/// case only TopK with offset=0 and limit=1 (aka Top1) for now. This is because (1)
/// Top1 can merge in each incremental row in constant space and time while the
/// generalized solution needs something like a priority queue and (2) we expect Top1
/// will be a common pattern used to turn a Kafka source's "upsert" semantics into
/// differential's semantics. (2) is especially interesting because Kafka is
/// monotonic with an ENVELOPE of NONE, which is the default for ENVELOPE in
/// Materialize and commonly used by users.
#[derive(Clone, Debug, Serialize, Deserialize)]
pub struct MonotonicTop1Plan {
/// The columns that form the key for each group.
pub group_key: Vec<usize>,
/// Ordering that is used within each group.
pub order_key: Vec<expr::ColumnOrder>,
}
/// A plan for monotonic TopKs with an offset of 0 and an arbitrary limit.
#[derive(Clone, Debug, Serialize, Deserialize)]
pub struct MonotonicTopKPlan {
/// The columns that form the key for each group.
pub group_key: Vec<usize>,
/// Ordering that is used within each group.
pub order_key: Vec<expr::ColumnOrder>,
/// Optionally, an upper bound on the per-group ordinal position of the
/// records to produce from each group.
pub limit: Option<usize>,
/// The number of columns in the input and output.
pub arity: usize,
}
/// A plan for generic TopKs that don't fit any more specific category.
#[derive(Clone, Debug, Serialize, Deserialize)]
pub struct BasicTopKPlan {
/// The columns that form the key for each group.
pub group_key: Vec<usize>,
/// Ordering that is used within each group.
pub order_key: Vec<expr::ColumnOrder>,
/// Optionally, an upper bound on the per-group ordinal position of the
/// records to produce from each group.
pub limit: Option<usize>,
/// A lower bound on the per-group ordinal position of the records to
/// produce from each group.
///
/// This can be set to zero to have no effect.
pub offset: usize,
/// The number of columns in the input and output.
pub arity: usize,
}