Skip to content

docs: Explain why event_timestamp is required in entity_df#6038

Open
Br1an67 wants to merge 1 commit intofeast-dev:masterfrom
Br1an67:docs/event-timestamp-explanation
Open

docs: Explain why event_timestamp is required in entity_df#6038
Br1an67 wants to merge 1 commit intofeast-dev:masterfrom
Br1an67:docs/event-timestamp-explanation

Conversation

@Br1an67
Copy link

@Br1an67 Br1an67 commented Mar 1, 2026

What this PR does / why we need it:

Expands the "Event timestamp" section in the feature retrieval concepts page to explain:

  • Why event_timestamp is required in the entity dataframe passed to get_historical_features()
  • How point-in-time joins work (Feast retrieves the latest feature values at or before the entity row's timestamp)
  • How this prevents data leakage during model training
  • A concrete example illustrating the behavior

Also adds inline comments in the quickstart code example to clarify the role of event_timestamp.

Which issue(s) this PR fixes:

Fixes #5555

Misc

Documentation-only change (2 files: docs/getting-started/concepts/feature-retrieval.md and docs/getting-started/quickstart.md).


Open with Devin

Expand the Event timestamp section in the feature retrieval concepts
page to explain:
- Why event_timestamp is required in the entity dataframe
- How point-in-time joins work (last known good value temporal join)
- How this prevents data leakage during model training
- A concrete example illustrating the behavior

Also add inline comments in the quickstart code example.
Copy link
Contributor

@devin-ai-integration devin-ai-integration bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no bugs or issues to report.

Open in Devin Review

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Documentation of event_timestamp in entity_df

1 participant