From 1b3c6140e7d1bfe561283e3677f384c404b91d52 Mon Sep 17 00:00:00 2001 From: Pengyu Hou <3771747+better365@users.noreply.github.com> Date: Mon, 5 Feb 2024 13:12:56 -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 | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/source/authoring_features/ChainingFeatures.md b/docs/source/authoring_features/ChainingFeatures.md index 006cb4687..54bdc69e5 100644 --- a/docs/source/authoring_features/ChainingFeatures.md +++ b/docs/source/authoring_features/ChainingFeatures.md @@ -6,7 +6,7 @@ For example, compute “average price of the last 10 items that a user purchase 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. -Assuming that square footage of a listing is stored separately from listing views - computing this requires +Computing this would require:``` - computing last_k items purchased per user, from the purchases stream - using the `item_id` to enrich the data with the `item_weight` - finally aggregating the item weight.