Skip to content

Commit 079395a

Browse files
committed
fix: Fix broken roadmap links (#2690)
Signed-off-by: Danny Chiao <[email protected]>
1 parent 40563ca commit 079395a

File tree

5 files changed

+7
-7
lines changed

5 files changed

+7
-7
lines changed

README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -176,7 +176,7 @@ The list below contains the functionality that contributors are planning to deve
176176
* [ ] Cassandra
177177
* **Streaming**
178178
* [x] [Custom streaming ingestion job support](https://docs.feast.dev/how-to-guides/creating-a-custom-provider)
179-
* [x] [Push based streaming data ingestion](https://docs.feast.dev/reference/data-sources/push.md)
179+
* [x] [Push based streaming data ingestion](https://docs.feast.dev/reference/data-sources/push)
180180
* [ ] Streaming ingestion on AWS
181181
* [ ] Streaming ingestion on GCP
182182
* **Feature Engineering**
@@ -207,7 +207,7 @@ The list below contains the functionality that contributors are planning to deve
207207
* [x] CLI for browsing feature registry
208208
* [x] Model-centric feature tracking (feature services)
209209
* [x] Amundsen integration (see [Feast extractor](https://github.com/amundsen-io/amundsen/blob/main/databuilder/databuilder/extractor/feast_extractor.py))
210-
* [x] Feast Web UI (Alpha release. See [documentation](https://docs.feast.dev/reference/alpha-web-ui.md))
210+
* [x] Feast Web UI (Alpha release. See [documentation](https://docs.feast.dev/reference/alpha-web-ui))
211211
* [ ] REST API for browsing feature registry
212212
* [ ] Feature versioning
213213

docs/getting-started/architecture-and-components/online-store.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,4 +12,4 @@ Once the above data source is materialized into Feast \(using `feast materialize
1212

1313
![](../../.gitbook/assets/image%20%285%29.png)
1414

15-
Features can also be written to the online store via [push sources](https://docs.feast.dev/reference/data-sources/push)
15+
Features can also be written to the online store via [push sources](../../reference/data-sources/push.md)

docs/getting-started/architecture-and-components/overview.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@ A complete Feast deployment contains the following components:
2323
* Materialize (load) feature values into the online store.
2424
* Build and retrieve training datasets from the offline store.
2525
* Retrieve online features.
26-
* **Online Store:** The online store is a database that stores only the latest feature values for each entity. The online store is populated by materialization jobs and from [stream ingestion](../../reference/alpha-stream-ingestion.md).
26+
* **Online Store:** The online store is a database that stores only the latest feature values for each entity. The online store is populated by materialization jobs and from [stream ingestion](../../reference/data-sources/push.md).
2727
* **Offline Store:** The offline store persists batch data that has been ingested into Feast. This data is used for producing training datasets. Feast does not manage the offline store directly, but runs queries against it.
2828

2929
{% hint style="info" %}

docs/getting-started/quickstart.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -367,7 +367,7 @@ pprint(feature_vector)
367367

368368
## Step 7: Using a feature service to fetch online features instead.
369369

370-
You can also use feature services to manage multiple features, and decouple feature view definitions and the features needed by end applications. The feature store can also be used to fetch either online or historical features using the same api below. More information can be found [here](https://docs.feast.dev/getting-started/concepts/feature-service).
370+
You can also use feature services to manage multiple features, and decouple feature view definitions and the features needed by end applications. The feature store can also be used to fetch either online or historical features using the same api below. More information can be found [here](https://docs.feast.dev/getting-started/concepts/feature-retrieval).
371371

372372
{% tabs %}
373373
{% tab title="Python" %}

docs/roadmap.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -41,7 +41,7 @@ The list below contains the functionality that contributors are planning to deve
4141
* [ ] Cassandra
4242
* **Streaming**
4343
* [x] [Custom streaming ingestion job support](https://docs.feast.dev/how-to-guides/creating-a-custom-provider)
44-
* [x] [Push based streaming data ingestion](https://docs.feast.dev/reference/data-sources/push.md)
44+
* [x] [Push based streaming data ingestion](https://docs.feast.dev/reference/data-sources/push)
4545
* [ ] Streaming ingestion on AWS
4646
* [ ] Streaming ingestion on GCP
4747
* **Feature Engineering**
@@ -72,6 +72,6 @@ The list below contains the functionality that contributors are planning to deve
7272
* [x] CLI for browsing feature registry
7373
* [x] Model-centric feature tracking (feature services)
7474
* [x] Amundsen integration (see [Feast extractor](https://github.com/amundsen-io/amundsen/blob/main/databuilder/databuilder/extractor/feast_extractor.py))
75-
* [x] Feast Web UI (Alpha release. See [documentation](https://docs.feast.dev/reference/alpha-web-ui.md))
75+
* [x] Feast Web UI (Alpha release. See [documentation](https://docs.feast.dev/reference/alpha-web-ui))
7676
* [ ] REST API for browsing feature registry
7777
* [ ] Feature versioning

0 commit comments

Comments
 (0)