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
Copy file name to clipboardExpand all lines: module_0/README.md
+5-4Lines changed: 5 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -528,10 +528,11 @@ There are two ways data scientists can use Feast:
528
528
- This is **not recommended** since data scientists cannot register feature services to indicate they depend on certain features in production.
529
529
- **[Recommended]** Have a local copy of the feature repository (e.g. `git clone`) and author / iterate / re-use features.
530
530
- Data scientist can:
531
-
1. iterate on features locally
532
-
2. apply features to their own dev project with a local registry & experiment
533
-
3. build feature services in preparation for production
534
-
4. submit PRs to include features that should be used in production (including A/B experiments, or model training iterations)
531
+
1. browse relevant features that are already productionized to re-use
532
+
2. iterate on new features locally
533
+
3. apply features to their own dev project with a local registry & experiment
534
+
4. build feature services in preparation for production
535
+
5. submit PRs to include features that should be used in production (including A/B experiments, or model training iterations)
535
536
536
537
Data scientists can also investigate other models and their dependent features / data sources / on demand transformations through the repository or through the Web UI (by running `feast ui`)
0 commit comments