GitBook: [v0.10-branch] 7 pages and 18 assets modified

feast-dev · Apr 30, 2021 · 8758256 · 8758256
1 parent e508700
commit 8758256
Show file tree

Hide file tree

Showing 17 changed files with 19 additions and 17 deletions.
diff --git a/...g-post-page-5 (1) (1) (1) (2) (2) (1).png → ...st-page-5 (1) (1) (1) (2) (2) (5) (1).png b/...g-post-page-5 (1) (1) (1) (2) (2) (1).png → ...st-page-5 (1) (1) (1) (2) (2) (5) (1).png
diff --git a/...g-post-page-5 (1) (1) (1) (2) (2) (2).png → ...st-page-5 (1) (1) (1) (2) (2) (5) (2).png b/...g-post-page-5 (1) (1) (1) (2) (2) (2).png → ...st-page-5 (1) (1) (1) (2) (2) (5) (2).png
diff --git a/...g-post-page-5 (1) (1) (1) (2) (2) (3).png → ...st-page-5 (1) (1) (1) (2) (2) (5) (3).png b/...g-post-page-5 (1) (1) (1) (2) (2) (3).png → ...st-page-5 (1) (1) (1) (2) (2) (5) (3).png
diff --git a/...g-post-page-5 (1) (1) (1) (2) (2) (4).png → ...st-page-5 (1) (1) (1) (2) (2) (5) (4).png b/...g-post-page-5 (1) (1) (1) (2) (2) (4).png → ...st-page-5 (1) (1) (1) (2) (2) (5) (4).png
diff --git a/...-blog-post-page-5 (1) (1) (1) (2) (2).png → ...st-page-5 (1) (1) (1) (2) (2) (5) (5).png b/...-blog-post-page-5 (1) (1) (1) (2) (2).png → ...st-page-5 (1) (1) (1) (2) (2) (5) (5).png
diff --git a/...book/assets/feast-landing-page-blog-post-page-5 (1) (1) (1) (2) (2) (5) (6).png b/...book/assets/feast-landing-page-blog-post-page-5 (1) (1) (1) (2) (2) (5) (6).png
diff --git a/...book/assets/feast-landing-page-blog-post-page-5 (1) (1) (1) (2) (2) (5) (7).png b/...book/assets/feast-landing-page-blog-post-page-5 (1) (1) (1) (2) (2) (5) (7).png
diff --git a/...) (2) (2) (2) (2) (2) (2) (2) (2) (1).png → ...) (2) (2) (2) (2) (2) (2) (2) (3) (1).png b/...) (2) (2) (2) (2) (2) (2) (2) (2) (1).png → ...) (2) (2) (2) (2) (2) (2) (2) (3) (1).png
diff --git a/...) (2) (2) (2) (2) (2) (2) (2) (2) (2).png → ...) (2) (2) (2) (2) (2) (2) (2) (3) (2).png b/...) (2) (2) (2) (2) (2) (2) (2) (2) (2).png → ...) (2) (2) (2) (2) (2) (2) (2) (3) (2).png
diff --git a/...) (2) (2) (2) (2) (2) (2) (2) (2) (2).png → ...) (2) (2) (2) (2) (2) (2) (2) (3) (3).png b/...) (2) (2) (2) (2) (2) (2) (2) (2) (2).png → ...) (2) (2) (2) (2) (2) (2) (2) (3) (3).png
diff --git a/docs/community.md b/docs/community.md
@@ -6,7 +6,7 @@
 
 ## Links & Resources
 
-* [Slack](https://join.slack.com/t/tectonfeast/shared_invite/zt-n7pl8gnb-H7dLlH9yQsgbchOp36ZUxQ): Feel free to ask questions or say hello!
+* [Slack](https://slack.feast.dev): Feel free to ask questions or say hello!
 * [Mailing list](https://groups.google.com/d/forum/feast-dev): We have both a user and developer mailing list.
   * Feast users should join [feast-discuss@googlegroups.com](mailto:feast-discuss@googlegroups.com) group by clicking [here](https://groups.google.com/g/feast-discuss).
   * Feast developers should join [feast-dev@googlegroups.com](mailto:feast-dev@googlegroups.com) group by clicking [here](https://groups.google.com/d/forum/feast-dev).

diff --git a/docs/concepts/apply.md b/docs/concepts/apply.md
@@ -2,17 +2,17 @@
 
 The `apply` command is used to persist your feature definitions in the feature registry and to configure or provision the necessary infrastructure for your feature store to operate
 
-### What happens during `feast apply`?
+## What happens during `feast apply`?
 
-#### 1. Scan the Feature Repository
+### 1. Scan the Feature Repository
 
 Feast will scan Python files in your feature repository, and find all Feast object definitions, such as feature views, entities, and data sources.
 
-#### 2. Update metadata
+### 2. Update metadata
 
 If all definitions look valid, Feast will sync the metadata about Feast objects to the registry. The registry is a tiny database storing most of the same information you have in the feature repository. This step is necessary because the production feature serving infrastructure won't be able to access Python files in the feature repository at run time, but it will be able to efficiently and securely read the feature definitions from the registry.
 
-#### 3. Create cloud infrastructure
+### 3. Create cloud infrastructure
 
 Feast CLI will create all necessary infrastructure for feature serving and materialization to work. What exactly gets created depends on which provider is configured to be used in `feature_store.yaml` in the feature repository.
 

diff --git a/docs/concepts/feature-repository.md b/docs/concepts/feature-repository.md
@@ -64,7 +64,7 @@ The `feature_store.yaml` file configures how the feature store should run. See [
 This file contains paths that should be ignored when running `feast apply`. An example `.feastignore` is shown below:
 
 {% code title=".feastignore" %}
-```
+```text
 # Ignore virtual environment
 venv
 
@@ -122,3 +122,4 @@ To declare new feature definitions, just add code to the feature repository, eit
 
 * See [Create a feature repository](../how-to-guides/create-a-feature-repository.md) to get started with an example feature repository.
 * See [feature\_store.yaml](../reference/feature-store-yaml.md), [.feastignore](../reference/feast-ignore.md) or [Feature Views](feature-views.md) for more information on the configuration files that live in a feature registry.
+
diff --git a/docs/feast-on-kubernetes/concepts/overview.md b/docs/feast-on-kubernetes/concepts/overview.md
@@ -10,7 +10,7 @@
 
 ## Concept Hierarchy
 
-![](../../.gitbook/assets/image%20%284%29%20%282%29%20%282%29%20%282%29%20%282%29%20%282%29%20%282%29%20%282%29%20%282%29%20%282%29%20%282%29%20%282%29%20%282%29%20%282%29%20%282%29.png)
+![](../../.gitbook/assets/image%20%284%29%20%282%29%20%282%29%20%282%29%20%282%29%20%282%29%20%282%29%20%282%29%20%282%29%20%282%29%20%282%29%20%282%29%20%282%29%20%282%29%20%283%29%20%282%29.png)
 
 Feast contains the following core concepts:
 

diff --git a/docs/quickstart.md b/docs/quickstart.md
@@ -165,7 +165,7 @@ entity_df.head()
 ```
 {% endcode %}
 
-![](.gitbook/assets/feast-landing-page-blog-post-page-5%20%281%29%20%281%29%20%281%29%20%282%29%20%282%29%20%282%29.png)
+![](.gitbook/assets/feast-landing-page-blog-post-page-5%20%281%29%20%281%29%20%281%29%20%282%29%20%282%29%20%285%29%20%285%29.png)
 
 This DataFrame represents the entity keys and timestamps that we want feature values for. We can pass this Entity DataFrame into Feast, and Feast will fetch point-in-time correct features for each row:
 

diff --git a/docs/reference/feast-ignore.md b/docs/reference/feast-ignore.md
@@ -5,7 +5,7 @@
 `.feastignore` is a file that is placed at the root of the [Feature Repository](../concepts/feature-repository.md). This file contains paths that should be ignored when running `feast apply`. An example `.feastignore` is shown below:
 
 {% code title=".feastignore" %}
-```
+```text
 # Ignore virtual environment
 venv
 
@@ -24,9 +24,10 @@ scripts/**/foo.py
 
 ## Feast Ignore Patterns
 
-| Pattern           | Example matches                                          | Explanation                                                                                                          |
-| ----------------- | -------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------- |
-| venv              | venv/foo.py<br>venv/a/foo.py                             | You can specify a path to a specific directory. Everything in that directory will be ignored.                        |
-| scripts/foo.py    | scripts/foo.py                                           | You can specify a path to a specific file. Only that file will be ignored.                                           |
-| scripts/*.py      | scripts/foo.py<br>scripts/bar.py                         | You can specify asterisk (*) anywhere in the expression. An asterisk matches zero or more characters, except "/".    |
-| scripts/**/foo.py | scripts/foo.py<br>scripts/a/foo.py<br>scripts/a/b/foo.py | You can specify double asterisk (**) anywhere in the expression. A double asterisk matches zero or more directories. |
+| Pattern | Example matches | Explanation |
+| :--- | :--- | :--- |
+| venv | venv/foo.py venv/a/foo.py | You can specify a path to a specific directory. Everything in that directory will be ignored. |
+| scripts/foo.py | scripts/foo.py | You can specify a path to a specific file. Only that file will be ignored. |
+| scripts/\*.py | scripts/foo.py scripts/bar.py | You can specify asterisk \(\*\) anywhere in the expression. An asterisk matches zero or more characters, except "/". |
+| scripts/\*\*/foo.py | scripts/foo.py scripts/a/foo.py scripts/a/b/foo.py | You can specify double asterisk \(\*\*\) anywhere in the expression. A double asterisk matches zero or more directories. |
+
diff --git a/docs/roadmap.md b/docs/roadmap.md
@@ -4,10 +4,10 @@
 
 ### **New Functionality**
 
-1. Full local mode support (Sqlite and Parquet)
+1. Full local mode support \(Sqlite and Parquet\)
 2. Provider model for added extensibility
 3. Firestore support
-4. Native (No-Spark) BigQuery support
+4. Native \(No-Spark\) BigQuery support
 5. Added support for object store based registry
 6. Add support for FeatureViews
 7. Added support for infrastructure configuration through `apply`