[FSTORE-1424] Feature logging #396
Conversation
|
|
||
| You can log features and predictions by calling `feature_view.log`. The logged features are written periodically to the offline store. If you need it to be available immediately, call `feature_view.materialize_log`. | ||
|
|
||
| You can log either transformed or/and untransformed features. To get untransformed features, you can specify `transform=False` in `feature_view.get_batch_data` or `feature_view.get_feature_vector(s)`. Inference helper columns are returned along with the untransformed features. To get the transformed features, you can call `feature_view.transform_batch_data` or `feature_view.transform_feature_vector(s)`. Inference helper columns are not returned as transformed features. [link to transformed features]() |
There was a problem hiding this comment.
You can log either transformed or/and untransformed features (by transformed, we mean that the categorical/numerical features haven been encoded).
Inference helper columns are returned along with the untransformed features (if they have been defined in the feature view).
You are missing the URL here:
link to transformed features
There was a problem hiding this comment.
MDT does not only encode features, you can create new features. Also I modified it, inference helper columns are not returned in untransformed feature hence not logged.
|
|
||
| ## Deleting Logs | ||
|
|
||
| When log data is no longer needed, you might want to delete it to free up space and maintain data hygiene. This operation deletes the feature groups and recreates new ones. Scheduled materialization job and log timeline are reset as well. |
There was a problem hiding this comment.
The scheduled materialization job is reset as well.
What does the "log timeline" mean here?
There was a problem hiding this comment.
hudi commit timeline of the logging feature group
No description provided.