Expected Behavior

Create the BQ dataset in the location specified in feature_store.yaml if the dataset doesn't exists

Current Behavior

Always create the BQ dataset in the US, raising a dataset not found since the dataset is not located in the same region as the one specified in feature_store.yam config file

Steps to reproduce

use an bigquery offline_store with location set to EU in feature_store.yaml

Specifications

• Version:
• Platform:
• Subsystem:

Possible Solution

update feast.infra.offline_stores.bigquery._get_table_reference_for_new_entity() by adding a new dataset_location arg