What is point-in-time correctness in feature stores?
hardAnswer
- When constructing training data, for each event at time t, use only feature values known BEFORE t.
- Prevents leakage from future data into features.
- Requires: (1) features timestamped with .
- (2) join uses 'as-of' semantics: .
- (3) Feature store must maintain event log, not just current snapshot.
- Without PIT, training features reflect future information that won't exist at serve time.
Check yourself — multiple choice
- Random
- For each event at t, use only features known before t; requires timestamps + as-of joins + event log; prevents future leakage
- Just current
- Not real
PIT correctness: as-of joins + event log; prevents future leakage.
#features#data-quality
Practise MLOps & Data Quality
215 interview questions in this topic.
Related questions
- How do you handle missing values in a production pipeline?
- How do you guarantee online-offline feature consistency?
- How do you prove there is no training-serving skew?
- What is point-in-time correctness, and how does violating it look in practice?
- What is data drift and how do you detect it?
- How is concept drift different from data drift?