← 输入框|github.com|刷新
Skip to content

fix: Preserve colliding source timestamps in Dask retrieval - #7071

Open
AryanRG wants to merge 1 commit into
feast-dev:masterfrom
AryanRG:fix/dask-created-timestamp-collision
Open

AryanRG wants to merge 1 commit into
feast-dev:masterfrom
AryanRG:fix/dask-created-timestamp-collision

Conversation

@AryanRG

@AryanRG AryanRG commented Oct 26, 2026

Copy link
Copy Markdown

What this PR does / why we need it:

When a source created timestamp shares a name with a request column, Dask historical retrieval can read the request value instead. This can include a backfill created after the query time or remove a request column from the result.

Keep the source timestamp under a temporary name that cannot collide with request or feature columns. Regression tests cover timestamp filtering, preserved request data and multiple feature views.

Which issue(s) this PR fixes:

No existing issue.

Checks

  • I've made sure the tests are passing.
  • My commits are signed off (git commit -s)
  • My PR title follows conventional commits format

Testing Strategy

  • Unit tests
  • Integration tests
  • Manual tests
  • Testing is not required for this change

Focused tests and neighboring Dask tests pass, along with scoped Ruff and mypy checks. The regression uses local Parquet files through the public FeatureStore API.

Signed-off-by: AryanRG <aryanrganjoo@gmail.com>
@AryanRG
AryanRG requested a review from a team as a code owner October 26, 2026 07:17

This branch has not been deployed

No deployments
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.

1 participant