[BUG] useLatestFeatureData doesn't use the latest feature data, but use "today's" feature data (which might not exist) · feathr-ai/feathr#898

(0 comments) (0 reactions) (0 assignees)Scala (1,929 stars) (244 forks)batch import

buggood first issue

説明

Willingness to contribute

No. I cannot contribute a bug fix at this time.

Feathr version

0.9.0

System information

Describe the problem

When using joinTimeSettings: { useLatestFeatureData: true }, Feathr uses LocalDateTime.now() to get the join time range. This results in None features if the feature's date is not "today".

Expected behavior is to use the max timestamp value from the feature data source so that it actually joins the "latest" feature data available.

Tracking information

No response

Code to reproduce bug

No response

What component(s) does this bug affect?

Python Client: This is the client users use to interact with most of our API. Mostly written in Python.
Computation Engine: The computation engine that execute the actual feature join and generation work. Mostly in Scala and Spark.
Feature Registry API: The frontend API layer supports SQL, Purview(Atlas) as storage. The API layer is in Python(FAST API)
Feature Registry Web UI: The Web UI for feature registry. Written in React

コントリビューターガイド

技術スタック: scala
領域: backenddata
Issue 種別: bug
難度: 3
推定時間: half day
活動状況: fresh
明確さ: mostly clear
前提条件: Scala basicsSpark conceptsFeathr join semantics
初心者向け度: 35
調査方針: The bug is in the computation engine (Scala/Spark). The issue states that `useLatestFeatureData: true` causes `LocalDateTime.now()` to be used instead of the max timestamp from the feature data. Look for the join logic that handles `useLatestFeatureData` in the Scala source code, likely in the feature join or observation generation components. Search for `useLatestFeatureData` in the repository to locate relevant files. The fix would involve replacing the current date call with a query to get the maximum timestamp from the feature source.