| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
Signed-off-by: Jun Ki Min <42475935+loomlike@users.noreply.github.com>
Signed-off-by: Jun Ki Min <42475935+loomlike@users.noreply.github.com>
Signed-off-by: Jun Ki Min <42475935+loomlike@users.noreply.github.com>
Signed-off-by: Jun Ki Min <42475935+loomlike@users.noreply.github.com>
…p range and fix issues Signed-off-by: Jun Ki Min <42475935+loomlike@users.noreply.github.com>
Signed-off-by: Jun Ki Min <42475935+loomlike@users.noreply.github.com>
| Back | FazBrowse Home | New Git URL |
Description
This PR resolves #899
to expose join time range functionality to python API.
I'm making this as a draft PR to open discussion about join config and fix potential issues -- currently, relative and absolute time range doesn't have any effect while useLatestFeatureData works.
Please check python's unit-tests (feathr_project/test/unit/definition/test_settings.py) and integration test (feathr_project/test/integration/test_observation_settings.py) to see if the function is implemented correctly, align with the join format.
Regarding an expected behavior of useLatestFeatureData, I opened another issue #898.
How was this PR tested?
Unit and integration tests
Does this PR introduce any user-facing changes?