Expected Behavior
Feature views should have the creation time (i.e., created_timestamp) at the first feast apply
Current Behavior
Features Views do not have creation time at feature view creation
Steps to reproduce
feast init fs
cd fs
feast apply
feast registry-dump
{
"spec": {
"name": "driver_id",
"valueType": "INT64",
"description": "driver id",
"joinKey": "driver_id"
},
"meta": {}
}
{
"spec": {
"name": "driver_hourly_stats",
"entities": [
"driver_id"
],
"features": [
{
"name": "conv_rate",
"valueType": "FLOAT"
},
{
"name": "acc_rate",
"valueType": "FLOAT"
},
{
"name": "avg_daily_trips",
"valueType": "INT64"
}
],
"ttl": "86400s",
"batchSource": {
"type": "BATCH_FILE",
"eventTimestampColumn": "event_timestamp",
"createdTimestampColumn": "created",
"fileOptions": {
"fileUrl": "/home/user/fs/data/driver_stats.parquet"
},
"dataSourceClassType": "feast.infra.offline_stores.file_source.FileSource"
},
"online": true
},
"meta": {}
Note that meta is empty.
Specifications
- Version: 0.12+
- Platform: Ubuntu 20.04.3 LTS
Possible Solution
Check if the feature view already have a creation date timpstamp (feature_view.created_timestamp) and then add datetime.now() if necessary. Possibly in the apply feature view method
Expected Behavior
Feature views should have the creation time (i.e.,
created_timestamp) at the firstfeast applyCurrent Behavior
Features Views do not have creation time at feature view creation
Steps to reproduce
Specifications
Possible Solution
Check if the feature view already have a creation date timpstamp (
feature_view.created_timestamp) and then adddatetime.now()if necessary. Possibly in the apply feature view method