-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Add offline retrival integration tests using the universal repo #1769
Add offline retrival integration tests using the universal repo #1769
Conversation
Signed-off-by: Achal Shah <[email protected]>
Codecov Report
@@ Coverage Diff @@
## master #1769 +/- ##
===========================================
- Coverage 84.65% 63.78% -20.87%
===========================================
Files 85 84 -1
Lines 6268 6415 +147
===========================================
- Hits 5306 4092 -1214
- Misses 962 2323 +1361
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
Signed-off-by: Achal Shah <[email protected]>
Signed-off-by: Achal Shah <[email protected]>
Signed-off-by: Achal Shah <[email protected]>
Signed-off-by: Achal Shah <[email protected]>
Signed-off-by: Achal Shah <[email protected]>
sdk/python/tests/integration/feature_repos/test_repo_configuration.py
Outdated
Show resolved
Hide resolved
Signed-off-by: Achal Shah <[email protected]>
Signed-off-by: Achal Shah <[email protected]>
Signed-off-by: Achal Shah <[email protected]>
sdk/python/tests/integration/feature_repos/test_repo_configuration.py
Outdated
Show resolved
Hide resolved
sdk/python/tests/integration/feature_repos/test_repo_configuration.py
Outdated
Show resolved
Hide resolved
sdk/python/tests/integration/feature_repos/test_repo_configuration.py
Outdated
Show resolved
Hide resolved
sdk/python/tests/integration/feature_repos/universal/data_sources/bigquery.py
Show resolved
Hide resolved
sdk/python/tests/integration/offline_store/test_universal_historical_retrieval.py
Outdated
Show resolved
Hide resolved
sdk/python/tests/integration/offline_store/test_universal_historical_retrieval.py
Outdated
Show resolved
Hide resolved
sdk/python/tests/integration/offline_store/test_universal_historical_retrieval.py
Outdated
Show resolved
Hide resolved
sdk/python/tests/integration/offline_store/test_universal_historical_retrieval.py
Outdated
Show resolved
Hide resolved
Signed-off-by: Achal Shah <[email protected]>
Signed-off-by: Achal Shah <[email protected]>
Signed-off-by: Achal Shah <[email protected]>
Signed-off-by: Achal Shah <[email protected]>
Signed-off-by: Achal Shah <[email protected]>
Signed-off-by: Achal Shah <[email protected]>
Signed-off-by: Achal Shah <[email protected]>
Signed-off-by: Achal Shah <[email protected]>
) | ||
assert_frame_equal(actual_df_from_sql_entities, df_from_sql_entities) | ||
|
||
# timestamp_column = ( |
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.
remove these?
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.
or if you want to fix it, consider moving into separate test as I suggest below
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.
I'm going to remove them because the behaviour isn't actually consistent across offline stores. File sources don't support sql queries at all.
# ], | ||
# ) | ||
|
||
job_from_df = store.get_historical_features( |
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.
thoughts on splitting sql vs df into two separate tests with the same initial setup? would make it so one can distinguish from test failures whether their bug is in common logic or logic specific to sql vs df
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.
I think a single test is better - sql and df params are testing the same API roughly, and tests will run faster if there's fewer separate tests.
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: achals, adchia The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Signed-off-by: Achal Shah <[email protected]>
/lgtm |
Signed-off-by: Achal Shah [email protected]
What this PR does / why we need it:
We wanna start parameterizing over all the possible combinations when reading feature values from the offline feature store. This PR introduces the decorator needed to set up the underlying tables as needed, updates the historical integration test to operate on an Environment object.
Which issue(s) this PR fixes:
Fixes #
Does this PR introduce a user-facing change?: