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
{{ message }}
Repository navigation
Commit a8cc117
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: docs/reference/online-stores/milvus.md
+99-3Lines changed: 99 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,20 +1,23 @@
1
-
# Redis online store
1
+
# Milvus online store
2
2
3
3
## Description
4
4
5
5
The [Milvus](https://milvus.io/) online store provides support for materializing feature values into Milvus.
6
6
7
7
* The data model used to store feature values in Milvus is described in more detail [here](../../specs/online\_store\_format.md).
8
+
* Multi-tenancy behavior is controlled by the `multi_tenancy_mode` setting (see below).
8
9
9
10
## Getting started
10
11
In order to use this online store, you'll need to install the Milvus extra (along with the dependency needed for the offline store of choice). E.g.
11
12
12
13
`pip install 'feast[milvus]'`
13
14
14
-
You can get started by using any of the other templates (e.g. `feast init -t gcp` or `feast init -t snowflake` or `feast init -t aws`), and then swapping in Redis as the online store as seen below in the examples.
15
+
You can get started by using any of the other templates (e.g. `feast init -t gcp` or `feast init -t snowflake` or `feast init -t aws`), and then swapping in Milvus as the online store as seen below in the examples.
Feast supports three mutually exclusive multi-tenancy strategies for Milvus. Set `multi_tenancy_mode` to make intent explicit; legacy configs are inferred for backwards compatibility.
61
+
62
+
- `none` (default): single-tenant; disallows `db_name` and `collection_name_prefix`
63
+
- `database`: per-tenant database isolation; requires `db_name`; forbids `collection_name_prefix`; not supported with local (Milvus Lite) mode
For multi-tenant environments, you can use database-level isolation by specifying the `db_name` parameter. This creates a separate Milvus database for each tenant, providing logical isolation of collections and data:
The full set of configuration options is available in [MilvusOnlineStoreConfig](https://rtd.feast.dev/en/latest/#feast.infra.online_stores.milvus.MilvusOnlineStoreConfig).
39
134
@@ -61,5 +156,6 @@ Below is a matrix indicating which functionality is supported by the Milvus onli
61
156
| collocated by feature service | no |
62
157
| collocated by entity key | no |
63
158
| vector similarity search | yes |
159
+
| database-level multi-tenancy | yes |
64
160
65
161
To compare this set of functionality against other online stores, please see the full [functionality matrix](overview.md#functionality-matrix).
0 commit comments