-
Notifications
You must be signed in to change notification settings - Fork 1.2k
guard timestamp_column in LocalDedupNode against missing DataFrame column #5985
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
faustaround
wants to merge
1
commit into
feast-dev:master
Choose a base branch
from
faustaround:fix/dedup-node-timestamp-column-keyerror
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🔴 Deduplication silently skipped when no timestamp columns are present in DataFrame
When neither
timestamp_columnnorcreated_timestamp_columnis present in the DataFrame columns,sort_keyswill be empty and theif sort_keys:guard at line 204 causes the entiredrop_duplicatescall to be skipped. This means duplicate rows (by join key) pass through undetected.Root Cause and Impact
The PR description states the intent is to "add a fallback to deduplicate by key only when no sort columns survive (rather than crashing)." However, the implementation at lines 204-207 simply skips deduplication entirely when
sort_keysis empty:When
sort_keysis empty (falsy), no deduplication happens at all. The correct behavior should be to still deduplicate bydedup_keysalone — just without a deterministic sort order. For example, using pandas'df.drop_duplicates(subset=dedup_keys)or equivalent.Impact: Any feature view where
timestamp_fieldis an internal bookkeeping column not exposed in the feature schema will have its timestamp column projected away before the dedup node runs. In this case, duplicate entity rows will silently remain in the output, leading to incorrect feature values (e.g., duplicated rows in training datasets or multiple values written to the online store for the same entity key).Was this helpful? React with 👍 or 👎 to provide feedback.