[FSTORE-1285] Model Dependent Transformation Functions #1140
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR implements required tables for Model Dependent Transformations:
Changes Done
Create new Table
feature_view_transformation_function
that maps feature view to corresponding transformation functions. It also stores the features that are used for the transformation as a string separated by commas in the columnfeatures
.Modified table
training_dataset_feature
to remove columntransformation_function_id
. This is done because transformation functions are mapped using "feature view's" instead of "training data set features" to allow support for many to many transformations.Modified table
transformation_function
to include columnsave_type
.save_type
denotes how the transformation functions are saved. It can currently have two value - "feature_view" or "feature_group". Transformation function that are implicitly register in the feature view would have thesave_type
as "feature_view" and the transformation function saved into the feature store using the existing API would have thesave_type
as "feature_store"