From 1242938502a8ccd6dd9ef812f1efa1705d169362 Mon Sep 17 00:00:00 2001 From: Pengyu Hou <3771747+better365@users.noreply.github.com> Date: Mon, 5 Feb 2024 13:12:26 -0800 Subject: [PATCH] Update docs/source/authoring_features/ChainingFeatures.md Co-authored-by: Varant Zanoyan Signed-off-by: Pengyu Hou <3771747+better365@users.noreply.github.com> --- docs/source/authoring_features/ChainingFeatures.md | 1 - 1 file changed, 1 deletion(-) diff --git a/docs/source/authoring_features/ChainingFeatures.md b/docs/source/authoring_features/ChainingFeatures.md index 721d1d673..ec5783b0d 100644 --- a/docs/source/authoring_features/ChainingFeatures.md +++ b/docs/source/authoring_features/ChainingFeatures.md @@ -5,7 +5,6 @@ Chaining Features refers to features which require weaving together transformati For example, compute “average price of the last 10 items that a user purchased”. This combines an initial `last_k` operation to get the "last 10 items" then applies an `average` operation on top of it as a chained aggregation. Or alternatively, "average weight of the last 10 items that a user purchased", but assuming that weight is not an included field in the purchases data, and rather stored in a normalized fashion in a different table. -These features cannot be expressed in single Join or GroupBy but need to be aggregated in several steps. Assuming that square footage of a listing is stored separately from listing views - computing this requires - computing last_k listings viewed per user first from a view stream and