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
{{ message }}
Repository navigation
Bug: Regression in BigQuery offline store caused by newer pydantic versions #4280
project: my_feature_reporegistry: gs://.../registry.db# The provider AWS used for the online store.# Mixing AWS and GCP should be okay provided that offline store type is specified.provider: awsoffline_store:
type: bigquerybilling_project_id: some-project-iddataset: latestgcs_staging_location: gs://...location: EUproject_id: some-project-idonline_store:
type: redisconnection_string: ...entity_key_serialization_version: 2
importos# Credentials for GCPos.environ["GOOGLE_APPLICATION_CREDENTIALS"]="GCP_keyfile.json"fromfeastimportFeatureStore, RepoConfigif__name__=="__main__":
# repo_path must contain the GCP_keyfile.json and feature_store.yaml filesrepo_path="./"assertos.path.exists(repo_path)
# Create a feature store objectstore=FeatureStore(repo_path=repo_path) # <--- Error occurs here
Specifications
Version: feast v0.38.0
Platform: x86-64 Ubuntu 22.04.3 LTS as well as arm64 Mac OS Sonoma 14.4.1
Subsystem:
Possible Solution
On first try, using values.data["project_id"] instead of values["project_id"] in the pydantic.field_validator for billing_project_id in bigquery.py#L108 should work:
@field_validator("billing_project_id")defproject_id_exists(cls, v, values, **kwargs):
# if v and not values["project_id"]:ifvandnotvalues.data["project_id"]:
raiseValueError(
"please specify project_id if billing_project_id is specified"
)
returnv
changed the title [-]Regression in BigQuery offline store caused by newer pydantic versions[/-][+]Bug: Regression in BigQuery offline store caused by newer pydantic versions[/+]on Jun 14, 2024
Same issue with feast v0.40.1. I have opened a PR. @galen-ft I just used your proposed solution for the issue. Have you made any progress on your end, or do you have any other ideas on how to fix it better or differently?
Hi @tokoko and @jgesche, and apologies for my late reply. I've been quite busy during the summer so I haven't had the chance to investigate a better fix. I'll try to do it as soon as I get some time.
Activity
[-]Regression in BigQuery offline store caused by newer pydantic versions[/-][+]Bug: Regression in BigQuery offline store caused by newer pydantic versions[/+]charlieviettq commentedon Jun 26, 2024
the same issue with
feastv0.39.0tokoko commentedon Jun 26, 2024
@galen-ft Let me know if you're planning to open a PR for this
jgesche commentedon Sep 10, 2024
Same issue with feast v0.40.1. I have opened a PR. @galen-ft I just used your proposed solution for the issue. Have you made any progress on your end, or do you have any other ideas on how to fix it better or differently?
galen-ft commentedon Sep 10, 2024
Hi @tokoko and @jgesche, and apologies for my late reply. I've been quite busy during the summer so I haven't had the chance to investigate a better fix. I'll try to do it as soon as I get some time.