Currently there is no distinction between user set values and system information about a feature set.
Proposing to add a larger FeatureSet object that holds both the user-specified spec and system-populated metadata of the feature set.
message FeatureSet {
// User-specified specifications of this feature set.
FeatureSetSpec spec = 1;
// System-populated metadata for this feature set.
FeatureSetMeta metadata = 2;
}
message FeatureSetSpec {
// same
}
message FeatureSetMeta {
// Created timestamp of this specific feature set.
google.protobuf.Timestamp created_timestamp = 1;
// Status of the feature set.
// Used to indicate whether the feature set is ready for consumption or ingestion.
// Currently supports 2 states:
// 1) PENDING - A feature set is in pending state if Feast has not spun up the jobs
// necessary to push rows for this feature set to stores subscribing to this feature set.
// 2) READY - Feature set is ready for consumption or ingestion
string status = 2;
// .. project, etc
}
Currently there is no distinction between user set values and system information about a feature set.
Proposing to add a larger FeatureSet object that holds both the user-specified
specand system-populatedmetadataof the feature set.