-
Notifications
You must be signed in to change notification settings - Fork 11
Make SparkOfflineStore compatible with interface change in feast>=0.17 #15
Conversation
Update readme to reflect Adyen template and add code owners
* Add github actions workflow based on python-package.yaml example * Black format repository * Install dev requirements with workflow * Update setup.py to only include dev as extra requires * Install package with dev requirements in github action workflow * Remove support for python 3.7 * Add workflow to publish to Python on release Co-authored-by: thijsbrits <thijsbrits@users.noreply.github.com>
This reverts commit 0a92c8c.
First release with bumped version
Bump version to 0.0.4
# interface of offline_utils.get_feature_view_query_context changed in feast==0.17 | ||
arg_spec = inspect.getfullargspec(func=offline_utils.get_feature_view_query_context) | ||
if "entity_df_timestamp_range" in arg_spec.args: | ||
# for feast>=0.17 |
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 see we're trying to support across few versions; we should update requirements in setup.py
to reflect that.
I't also be fine dropping support for older versions altogether. Users of this plugin can update it when updating feast
in one-go.
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.
setup.py
mentions feast>=0.15.0
which is correct. If we'd choose to not support backwards compatibility we would have to update the requirements.
I vote to keep it like this for now, this also allows us to decouple upgrading feast
from upgrading feast-spark-offline-store
Summary
SparkOfflineStore
functionality to work withfeast>=0.17
setuptools_scm
for versioningmain
that were not included in upstreamdevelop
Tested scenarios
Ran all tests
Fixed issue
#14