Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: Fix broken roadmap links #2690

Merged
merged 1 commit into from
May 13, 2022
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -176,7 +176,7 @@ The list below contains the functionality that contributors are planning to deve
* [ ] Cassandra
* **Streaming**
* [x] [Custom streaming ingestion job support](https://docs.feast.dev/how-to-guides/creating-a-custom-provider)
* [x] [Push based streaming data ingestion](https://docs.feast.dev/reference/data-sources/push.md)
* [x] [Push based streaming data ingestion](https://docs.feast.dev/reference/data-sources/push)
* [ ] Streaming ingestion on AWS
* [ ] Streaming ingestion on GCP
* **Feature Engineering**
Expand Down Expand Up @@ -207,7 +207,7 @@ The list below contains the functionality that contributors are planning to deve
* [x] CLI for browsing feature registry
* [x] Model-centric feature tracking (feature services)
* [x] Amundsen integration (see [Feast extractor](https://github.com/amundsen-io/amundsen/blob/main/databuilder/databuilder/extractor/feast_extractor.py))
* [x] Feast Web UI (Alpha release. See [documentation](https://docs.feast.dev/reference/alpha-web-ui.md))
* [x] Feast Web UI (Alpha release. See [documentation](https://docs.feast.dev/reference/alpha-web-ui))
* [ ] REST API for browsing feature registry
* [ ] Feature versioning

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -12,4 +12,4 @@ Once the above data source is materialized into Feast \(using `feast materialize

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

Features can also be written to the online store via [push sources](https://docs.feast.dev/reference/data-sources/push)
Features can also be written to the online store via [push sources](../../reference/data-sources/push.md)
Original file line number Diff line number Diff line change
Expand Up @@ -23,7 +23,7 @@ A complete Feast deployment contains the following components:
* Materialize (load) feature values into the online store.
* Build and retrieve training datasets from the offline store.
* Retrieve online features.
* **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).
* **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).
* **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.

{% hint style="info" %}
Expand Down
2 changes: 1 addition & 1 deletion docs/getting-started/quickstart.md
Original file line number Diff line number Diff line change
Expand Up @@ -367,7 +367,7 @@ pprint(feature_vector)

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

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).
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).

{% tabs %}
{% tab title="Python" %}
Expand Down
4 changes: 2 additions & 2 deletions docs/roadmap.md
Original file line number Diff line number Diff line change
Expand Up @@ -41,7 +41,7 @@ The list below contains the functionality that contributors are planning to deve
* [ ] Cassandra
* **Streaming**
* [x] [Custom streaming ingestion job support](https://docs.feast.dev/how-to-guides/creating-a-custom-provider)
* [x] [Push based streaming data ingestion](https://docs.feast.dev/reference/data-sources/push.md)
* [x] [Push based streaming data ingestion](https://docs.feast.dev/reference/data-sources/push)
* [ ] Streaming ingestion on AWS
* [ ] Streaming ingestion on GCP
* **Feature Engineering**
Expand Down Expand Up @@ -72,6 +72,6 @@ The list below contains the functionality that contributors are planning to deve
* [x] CLI for browsing feature registry
* [x] Model-centric feature tracking (feature services)
* [x] Amundsen integration (see [Feast extractor](https://github.com/amundsen-io/amundsen/blob/main/databuilder/databuilder/extractor/feast_extractor.py))
* [x] Feast Web UI (Alpha release. See [documentation](https://docs.feast.dev/reference/alpha-web-ui.md))
* [x] Feast Web UI (Alpha release. See [documentation](https://docs.feast.dev/reference/alpha-web-ui))
* [ ] REST API for browsing feature registry
* [ ] Feature versioning