[BUG] useLatestFeatureData doesn't use the latest feature data, but use "today's" feature data (which might not exist)

Willingness to contribute

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

Feathr version

0.9.0

System information

NA

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