You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When calling the materialize functionality to materialize data from a SnowflakeSource offline store to a local PostgreSQLOnlineStore, the table is not populated with the data.
Current Behavior
The feature table in the local Postgres instance is not populated, while no exception is raised, and from the logs it seems like the data should be pushed to Postgres.
Steps to reproduce
Use this feature_store.yaml file:
project: my_project
provider: local
registry:
registry_type: sql
path: postgresql://postgres:test@0.0.0.0:5432/feature_store
cache_ttl_seconds: 60
online_store:
type: postgres
host: 0.0.0.0
port: 5432
database: feature_store
db_schema: public
user: postgres
password: test
offline_store:
<SNOWFLAKE_INFORMATION>
entity_key_serialization_version: 2
It seems like a conn.commit() statement is missing in the online_write_batch method of the PostgreSQLOnlineStore. Specifically, on this line.
After adding this, the table is populated.
The PR implementing this proposed fix can be found here.
Additional notes
When replacing the the postgres online store with the following sqlite online store in the config file, everything works without any code changes
Expected Behavior
When calling the
materialize
functionality to materialize data from aSnowflakeSource
offline store to a localPostgreSQLOnlineStore
, the table is not populated with the data.Current Behavior
The feature table in the local Postgres instance is not populated, while no exception is raised, and from the logs it seems like the data should be pushed to Postgres.
Steps to reproduce
Specifications
Possible Solution
It seems like a
conn.commit()
statement is missing in theonline_write_batch
method of thePostgreSQLOnlineStore
. Specifically, on this line.After adding this, the table is populated.
The PR implementing this proposed fix can be found here.
Additional notes
When replacing the the postgres online store with the following sqlite online store in the config file, everything works without any code changes
The text was updated successfully, but these errors were encountered: