-
Notifications
You must be signed in to change notification settings - Fork 1.3k
chore: Update docs for offline and online stores #2946
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
Changes from 1 commit
b70c64b
7343857
a9f6027
df11468
dc26144
fdfbb75
6adff74
c4b2519
977221f
846f5fe
6a85ce2
d000842
2694894
98134bf
b61f034
69405df
6d9f507
76eab5c
aad3dba
3945684
5484ba6
1cc81e2
e5ecd48
e20e6c9
76353a3
b071dc7
6aadfca
392595a
ea7c982
a34cdba
efa51b1
5bc74db
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
Signed-off-by: Kevin Zhang <kzhang@tecton.ai>
- Loading branch information
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -329,17 +329,17 @@ Even if you have created the `OnlineStore` class in a separate repo, you can sti | |
| - Feast parametrizes integration tests using the `FULL_REPO_CONFIGS` variable defined in `sdk/python/tests/integration/feature_repos/repo_configuration.py` which stores different online store classes for testing. | ||
| - To overwrite these configurations, you can simply create your own file that contains a `FULL_REPO_CONFIGS` variable, and point Feast to that file by setting the environment variable `FULL_REPO_CONFIGS_MODULE` to point to that file. | ||
|
|
||
| A sample `FULL_REPO_CONFIGS_MODULE` looks something like this: | ||
| A sample `FULL_REPO_CONFIGS_MODULE` looks something like this: | ||
|
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. would follow the pattern of the other code snippets, which also include a "file title" that shows where this lives See the example of using: that we did before
Collaborator
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. fixed |
||
|
|
||
| {% code title="sdk/python/feast/infra/online_stores/contrib/postgres_repo_configuration.py" %} | ||
| ```python | ||
| from feast.infra.offline_stores.contrib.postgres_offline_store.tests.data_source import ( | ||
| PostgreSQLDataSourceCreator, | ||
| ) | ||
| {% code title="sdk/python/feast/infra/online_stores/contrib/postgres_repo_configuration.py" %} | ||
| ```python | ||
| from feast.infra.offline_stores.contrib.postgres_offline_store.tests.data_source import ( | ||
| PostgreSQLDataSourceCreator, | ||
| ) | ||
|
|
||
| AVAILABLE_ONLINE_STORES = {"postgres": (None, PostgreSQLDataSourceCreator)} | ||
| ``` | ||
| {% endcode %} | ||
| AVAILABLE_ONLINE_STORES = {"postgres": (None, PostgreSQLDataSourceCreator)} | ||
| ``` | ||
| {% endcode %} | ||
|
|
||
|
|
||
| If you are planning to start the online store up locally(e.g spin up a local Redis Instance) for testing, then the dictionary entry should be something like: | ||
|
|
||
Uh oh!
There was an error while loading. Please reload this page.