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
{{ message }}
Repository navigation
Commit 940f774
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: docs/reference/feature-store-yaml.md
+17Lines changed: 17 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -25,6 +25,23 @@ online_store:
25
25
* **project\_id** — Optional parameter for the datastore online store. Sets the GCP project id used by Feast, if not set Feast will use the default GCP project id in the local environment.
26
26
* **project** — Defines a namespace for the entire feature store. Can be used to isolate multiple deployments in a single installation of Feast.
27
27
28
+
### feature_server
29
+
30
+
The `feature_server` block configures the Python Feature Server when it is used
31
+
to serve online features and handle `/push` requests. This section is optional
32
+
and only applies when running the Python feature server.
33
+
34
+
An example configuration:
35
+
36
+
```yaml
37
+
feature_server:
38
+
type: local
39
+
offline_write_batching: # Enables batching of offline writes processed by /push. Online writes are unaffected.
40
+
enabled: true
41
+
batch_size: 100 # Maximum number of buffered rows before writing to the offline store.
42
+
batch_interval_seconds: 5 # Maximum time rows may remain buffered before a forced flush.
43
+
```
44
+
28
45
## Providers
29
46
30
47
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.
0 commit comments