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
Is your feature request related to a problem? Please describe.
When declaring a BigQuerySource, for the table parameter you must at a minimum provide <dataset>.<table_name>. This is despite already providing the <dataset> and <gcp-project> in the feature_store.yaml. This means that the dataset must either be hardcoded into the source declaration or you must provide some custom logic to keep it consistent across your repo (can be difficult if you set up is complex and multi modular).
Describe the solution you'd like
When no dataset is provided in the table parameter, default to using the configured dataset in the feature_store.yaml. This would allow users to quickly switch between datasets on the fly (when working locally we load data into user datasets for example).
Describe alternatives you've considered
Implementing custom logic on top of feast to keep it consistent but this doesn't fit nicely into our current code setup, it would be nice if Feast just used this already configured variable by default.
Additional context
N/a
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
When declaring a
BigQuerySource
, for thetable
parameter you must at a minimum provide<dataset>.<table_name>
. This is despite already providing the<dataset>
and<gcp-project>
in thefeature_store.yaml
. This means that the dataset must either be hardcoded into the source declaration or you must provide some custom logic to keep it consistent across your repo (can be difficult if you set up is complex and multi modular).Describe the solution you'd like
When no dataset is provided in the
table
parameter, default to using the configured dataset in thefeature_store.yaml
. This would allow users to quickly switch between datasets on the fly (when working locally we load data into user datasets for example).Describe alternatives you've considered
Implementing custom logic on top of feast to keep it consistent but this doesn't fit nicely into our current code setup, it would be nice if Feast just used this already configured variable by default.
Additional context
N/a
The text was updated successfully, but these errors were encountered: