How do you version features?
mediumAnswer
- (1) Each feature has definition (name + computation code + owner + description).
- (2) Version bumps on compute change .
- (3) Both versions computed in parallel during migration.
- (4) Models declare which feature versions they consume.
- (5) Deprecate old versions when no consumers.
- Tools: Feast Registry, Tecton Feature Views.
- Anti-pattern: silent feature computation change → all downstream models silently regress.
Check yourself — multiple choice
- Random
- Feature definition = name+code+owner+desc; version bumps on compute change; parallel computation during migration; models declare consumed versions; deprecate old
- No versioning
- Not real
Feature versioning: definition + version + parallel migration + deprecation.
#features#reproducibility
Practise MLOps & Data Quality
215 interview questions in this topic.
Related questions
- What problem does a feature store solve?
- How do you handle missing values in a production pipeline?
- How do you handle high-cardinality categorical features?
- How do you handle cold-start users / items in production?
- Why version data (DVC / lakeFS / Delta Lake)?
- What is data / model lineage and why does it matter?