GitBook: [master] 59 pages modified

Author: jparthasarthy

docs/SUMMARY.md

@@ -23,7 +23,7 @@
 
 ## Reference
 
-* [Repository Config](reference/repository-config.md)
+* [feature\_store.yaml](reference/feature-store-yaml.md)
 * [Python API reference](http://rtd.feast.dev/)
 
 ## Feast on Kubernetes

docs/concepts/feature-repository.md

@@ -45,7 +45,7 @@ online_store:
 * **Project**: A unique identifier for your project. The project name is used to isolate multiple feature stores when deploying to the same infrastructure. 
 * **Registry**: The registry is used to persist feature definitions and related metadata. The registry is updated when the `apply` command is run to update infrastructure. The registry is read when users try to build training datasets or try to read from an online store. A registry can either be a local file or a file on an object store \(if it needs to be shared\).
 * **Provider**: The provider defines the target environment that will be used to configure your infrastructure. By selecting `local`, Feast will configure local infrastructure for storing and serving features. By selecting `gcp`, Feast will configure cloud infrastructure for storing and serving features.
-* **Online Store**: This option allows teams to configure the destination online store that should be used to store and serve online features. The type of online store that can be selected and configured depends on the `provider`. One provider may allow more than one online store to be configured.
+* **Online Store**: This option allows teams to configure the destination online store that should be used to store and serve online features. The type of online store that can be selected and configured depends on the `provider`. A provider may allow more than one online store to be configured.
 
 ## Feature definitions
 

docs/quickstart.md

@@ -8,7 +8,7 @@ Welcome to the Feast quickstart! This quickstart is intended to get you up and r
 4. Materializing feature data to the online feature store
 5. Fetching feature vectors for inference
 
-The quickstart uses some example data about a ride hailing app to walk through Feast. Let's get into it!
+This quickstart uses some example data about a ride hailing app to walk through Feast. Let's get into it!
 
 ### 1. Setting up Feast
 
@@ -49,7 +49,7 @@ online_store:
         path: data/online_store.db
 ```
 
-This file defines how the feature store is configured to run.  The most important option here is `provider`, which specifies the environment that Feast will run in. We've initialized `provider=local`, indicating that Feast will run the feature store on our local machine. See [Repository Config](reference/repository-config.md) for more details.
+This file defines how the feature store is configured to run.  The most important option here is `provider`, which specifies the environment that Feast will run in. We've initialized `provider=local`, indicating that Feast will run the feature store on our local machine. See [Repository Config](reference/feature-store-yaml.md) for more details.
 
 Next, take a look at `example.py`. This file defines some example features:
 

docs/reference/feature-store-yaml.md

@@ -0,0 +1,52 @@
+# feature\_store.yaml
+
+### Overview
+
+`feature_store.yaml` is a file that is placed at the root of the [Feature Repository](../concepts/feature-repository.md). This file contains configuration about how the feature store runs. An example `feature_store.yaml` is shown below:
+
+{% code title="feature\_store.yaml" %}
+```yaml
+project: loyal_spider
+registry: data/registry.db
+provider: local
+online_store:
+    type: sqlite
+    path: data/online_store.db
+    
+
+```
+{% endcode %}
+
+### Fields in feature\_store.yaml
+
+* **provider** \("local" or "gcp"\)  — Defines the environment in which Feast will execute data flows.
+* **registry** \(a local or GCS filepath\) — Defines the location of the feature registry.
+* **online\_store** — Configures the online store. This field has two subfields:
+  * **type** \("sqlite" or "datastore"\) — Defines the type of online store.
+  * **path** \(a local filepath\) — Defines the path to the SQLite database file.
+* **project** — Defines a namespace for the entire feature store. Can be used to isolate multiple deployments in a single installation of Feast.
+
+### Providers
+
+The `provider` field defines the environment in which Feast will execute data flows. As a result, it also determines the default values for other fields.
+
+#### Local
+
+When using the local provider:
+
+* Feast can read from **Parquet data sources**,.
+* Feast performs historical feature retrieval \(point-in-time joins\) using **pandas.**
+* Feast performs online feature serving from a **SQLite database.**
+
+#### **GCP**
+
+When using the GCP provider:
+
+* Feast can read data from **BigQuery data sources.**
+* Feast performs historical feature retrieval \(point-in-time joins\) using **BigQuery.**
+* Feast performs online feature serving from **Google Cloud Firestore.**
+
+
+
+
+