hsfs.core.feature_logging #
FeatureLogging #
materialization_interval property #
materialization_interval: str | None
How often the logs are written to the offline store, "hour" or "day", or None for the platform default.
The backend keeps the cadence only as the materialization job's schedule, so a value that was not set in this session is read back from that schedule.
transport property #
transport: str | None
How logged rows reach the logging feature group, "realtime" or "job".
A feature view logs through one transport, and the layout of its logging feature group tells which: the realtime group is a stream group with an online copy, the job group is an offline-only Delta group filled by the commit job. None when logging has no feature group yet.
get_feature_group #
get_feature_group(
transformed: bool | None = None,
) -> feature_group.FeatureGroup
Get the feature group backing this feature logging.
Transformed and untransformed features are logged in the same feature group, so the same feature group is returned regardless of transformed.
| PARAMETER | DESCRIPTION |
|---|---|
transformed | Deprecated and ignored; kept for backwards compatibility. TYPE: |
| RETURNS | DESCRIPTION |
|---|---|
feature_group.FeatureGroup | The feature group used to store logged features. |