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
"Dataset" that was meant on the sdk is a collection of features selected by the user. While this term is also used in BigQuery, the SDK should not create a dataset whenever this function is called, rather just create a view in the feast dataset.
The idea of a dataset to the client should be a materialization of a feature set. Basically a collection of rows for specific columns (features). We should not care what happens in BQ in terms of naming (bq table vs dataset).
In this case I think it is important that we create a table as a snapshot of the data (not a BQ dataset) in order to make the dataset immutable. A view would not provide that. In the event that the user wants to have new data, they should create a new dataset using the same features and time range query.
Expected Behavior
"Dataset" that was meant on the sdk is a collection of features selected by the user. While this term is also used in BigQuery, the SDK should not create a dataset whenever this function is called, rather just create a view in the feast dataset.
Current Behavior
It creates a new BigQuery Dataset.
Steps to reproduce
Use the quickstart:
Specifications
Possible Solution
create_dataset
to create view in feast dataset insteadcreate_view
?The text was updated successfully, but these errors were encountered: