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
Housekeeping of Feast CI, docker compose, and notebooks (#916)
* Add caching to core and serving builds
* Fix flaky e2e tests
* Simplify docker-compose setup
* Add kafka broker to docker compose test
* Rename batch to historical
* Update troubleshooting.md
* Fix casing for FEAST_HISTORICAL_SERVING_URL
* Remove f-string prefix
* Fix missing key in docker compose setup
* Fix documentation typos
* Add jupyter to load test
* Add docker compose back to load-test
* Clean up FEAST_VERSION in load test
* Fix artifact output for load test
* Revert e2e test order
`netcat`, `telnet`, or even `curl` can be used to test whether all services are available and ports are open, but `grpc_cli` is the most powerful. It can be installed from [here](https://github.com/grpc/grpc/blob/master/doc/command_line_tool.md).
@@ -107,7 +107,7 @@ ListProjects
107
107
### Testing Feast Batch Serving and Online Serving
108
108
109
109
```bash
110
-
grpc_cli ls ${FEAST_BATCH_SERVING_URL} feast.serving.ServingService
110
+
grpc_cli ls ${FEAST_HISTORICAL_SERVING_URL} feast.serving.ServingService
111
111
```
112
112
113
113
```text
@@ -145,11 +145,11 @@ In order to print the logs from these services, please run the commands below.
Copy file name to clipboardExpand all lines: docs/getting-started/deploying-feast/docker-compose.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -80,12 +80,12 @@ Configure the `.env` file based on your environment. At the very least you have
80
80
| Parameter | Description |
81
81
| :--- | :--- |
82
82
|`FEAST_CORE_GCP_SERVICE_ACCOUNT_KEY`| This should be your service account file name, for example `key.json`. |
83
-
|`FEAST_BATCH_SERVING_GCP_SERVICE_ACCOUNT_KEY`| This should be your service account file name, for example `key.json`|
83
+
|`FEAST_HISTORICAL_SERVING_GCP_SERVICE_ACCOUNT_KEY`| This should be your service account file name, for example `key.json`|
84
84
|`FEAST_JUPYTER_GCP_SERVICE_ACCOUNT_KEY`| This should be your service account file name, for example `key.json`|
85
85
86
86
### 3.3 Configure Historical Serving
87
87
88
-
We will also need to configure the `batch-serving.yml` file inside `infra/docker-compose/serving/`. This configuration is used to retrieve training datasets from Feast. At a minimum you will need to set:
88
+
We will also need to configure the `historical-serving.yml` file inside `infra/docker-compose/serving/`. This configuration is used to retrieve training datasets from Feast. At a minimum you will need to set:
Copy file name to clipboardExpand all lines: docs/installation/docker-compose.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -85,7 +85,7 @@ Configure the `.env` file based on your environment. At the very least you have
85
85
| Parameter | Description |
86
86
| :--- | :--- |
87
87
| FEAST\_CORE\_GCP\_SERVICE\_ACCOUNT\_KEY | This should be your service account file name, for example `key.json`. |
88
-
| FEAST\_BATCH\_SERVING\_GCP\_SERVICE\_ACCOUNT\_KEY | This should be your service account file name, for example `key.json`|
88
+
| FEAST\_HISTORICAL\_SERVING\_GCP\_SERVICE\_ACCOUNT\_KEY | This should be your service account file name, for example `key.json`|
89
89
| FEAST\_JUPYTER\_GCP\_SERVICE\_ACCOUNT\_KEY | This should be your service account file name, for example `key.json`|
90
90
| FEAST\_JOB\_STAGING\_LOCATION | Google Cloud Storage bucket that Feast will use to stage data exports and batch retrieval requests, for example `gs://your-gcs-bucket/staging`|
Copy file name to clipboardExpand all lines: examples/feast-xgboost-churn-prediction-tutorial/Telecom Customer Churn Prediction (with Feast and XGBoost).ipynb
0 commit comments