May we use cookies so Meta, Google, LinkedIn and ChatGPT see your visit and we learn which ads work? PrivacyMay we use cookies to see which pages help, and let Meta, Google, LinkedIn and ChatGPT see your visit, so we know which of our ads work? That way we spend less on ads that do not work. We do not sell your data, and the site works the same if you decline. You can change your answer at any time under Cookie settings at the foot of the page. Privacy policy
Loading...
AI Engineering · Features And Feature Stores
Free preview: the first 2 parts of this 24-part lesson.
Already bought the course? Sign in to read the whole lesson.
this lesson is part of
Generative AI and Agentic AI Engineering
Unlock this lesson and the 208 other paid lessons
$35 once, by card or PayPal
See the Generative AI and Agentic AI courseread the rest of this lesson in
Generative AI and Agentic AI Engineering
Unlock this lesson and the 208 other paid lessons
$35 once, by card or PayPal
See the Generative AI and Agentic AI coursein Features And Feature Stores
This lesson is part of the AI Engineering course. Unlock the full course, a separate one-time payment, for lifetime access.
One-time payment by card or PayPal
Get Lifetime AccessOne-time payment: UPI, card or netbanking
Get Lifetime AccessFoundation lessons of this course are free, no payment needed. Try them now
Let me start with an office desk.
Imagine the front desk of a big office building. Every evening, the man at the desk writes up a tally of the day's post: how many letters came for each company in the building. Each letter has a postmark, the date it was sent. Most letters come the next morning. A few take days, because one post office was slow or one van broke down.
So every evening he has a choice. He can write up the tally now, and miss the letters that are still on their way. Or he can wait a day or two, catch most of the slow ones, and give the companies their tally later.

There is a second choice too. When a letter turns up after the tally is written, what does he do with it? He can add it to the next tally, or he can throw it away because its day is already closed.
A feature pipeline has exactly these two choices. This lesson measures what each one is worth, on data from a real shop, with one big warning that the next slides explain: the delays are invented.
This is the sixth lesson of the chapter on features and feature stores. It uses the same shop data, the same prediction task and the same model as the lessons before it.
The first lesson, what a feature is, built six made features from each customer's history: recency, frequency, money, return share, tenure and products. With those six, the default model reached a test average precision of 0.5450. In this lesson, the model with the true features is exactly that model, checked to the last digit on all 20 seeds.
The third lesson, feature freshness, asked how old a feature can be before it costs anything. On this task, features up to two weeks old cost nothing its tests could tell apart from zero. Keep that in mind. It is the main reason the result of this lesson is small.
The data engineering chapter's first lesson, batch vs streaming data, defined event time, processing time, watermarks and allowed lateness, with sources. Its lab could not measure them, because its data had no arrival times. I do not repeat those definitions in full here. This lesson measures what they do, as far as invented delays allow.