Title: make vector search configs part of feature definition · Issue #5652 · feast-dev/feast · GitHub
Open Graph Title: make vector search configs part of feature definition · Issue #5652 · feast-dev/feast
X Title: make vector search configs part of feature definition · Issue #5652 · feast-dev/feast
Description: Is your feature request related to a problem? Please describe. A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] Hello everyone, I have a question about the recommended pattern for using Milvus ...
Open Graph Description: Is your feature request related to a problem? Please describe. A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] Hello everyone, I have a question about t...
X Description: Is your feature request related to a problem? Please describe. A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] Hello everyone, I have a question abo...
Opengraph URL: https://github.com/feast-dev/feast/issues/5652
X: @github
Domain: github.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"make vector search configs part of feature definition","articleBody":"**Is your feature request related to a problem? Please describe.**\nA clear and concise description of what the problem is. Ex. I'm always frustrated when [...]\n\nHello everyone,\nI have a question about the recommended pattern for using Milvus as an online store in a multi-team environment.\nThe feature_store.yaml configuration for Milvus defines [global configs](https://docs.feast.dev/reference/online-stores/milvus#examples), like:\nembedding_dim\nindex_type\nmetric_type\nOur use case involves multiple teams (e.g., marketing, sales) sharing the feature store, but their vector embeddings have different requirements. For example:\nThe Marketing team might use a 768-dimension vector with COSINE similarity.\nThe Sales team might use a 128-dimension vector with L2 similarity.\nSince these configurations seem to be set at the online_store level, it implies we can only support one type of vector across the entire store. This would prevent us from sharing one feature server across teams with different vector models.\nWhat is the best way to support multiple, diverse vector feature views (with different dimensions, metrics, etc.) in a single Milvus online store?\nIs the intended pattern to create a separate online_store definition for each unique vector configuration, or am I misunderstanding how these parameters should be used?\nThanks for any insights!\n\n**Describe the solution you'd like**\nA clear and concise description of what you want to happen.\n\n**Describe alternatives you've considered**\nA clear and concise description of any alternative solutions or features you've considered.\n\n**Additional context**\nAdd any other context or screenshots about the feature request here.\n","author":{"url":"https://github.com/haoxu0","@type":"Person","name":"haoxu0"},"datePublished":"2025-10-07T17:09:37Z","url":"https://github.com/feast-dev/feast/issues/5652"}
| react-profiling | 0 |
| react-import-map | react,react-dom,react-dom/client,react-dom/profiling,react-is,react/compiler-runtime,react/jsx-dev-runtime,react/jsx-runtime,scheduler@b8488ee2c322 |
| route-pattern | /_view_fragments/issues/show/:user_id/:repository/:id/issue_layout(.:format) |
| route-controller | voltron_issues_fragments |
| route-action | issue_layout |
| fetch-nonce | v2:4ad6dac3-6ceb-356d-5fe1-c743a35b02b4 |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | E4F8:498F8:2D98B9:3F1C6D:6AFE980B |
| html-safe-nonce | b12525f8aaddd103951ce8d427a13a4e9a68641772966b1154a04b2c1a08c989 |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJFNEY4OjQ5OEY4OjJEOThCOTozRjFDNkQ6NkFGRTk4MEIiLCJ2aXNpdG9yX2lkIjoiNTQwNDgyMjU1OTczNDUzNjIwMyIsInJlZ2lvbl9lZGdlIjoiaWFkIiwicmVnaW9uX3JlbmRlciI6ImlhZCJ9 |
| visitor-hmac | 81fe5ab9d307d108e6d2880309de6b48003f1c1040a29b58c93d89b510018f72 |
| hovercard-subject-tag | issue:3492307714 |
| github-keyboard-shortcuts | repository,issues,copilot |
| google-site-verification | Apib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I |
| octolytics-url | https://collector.github.com/github/collect |
| analytics-location | / |
| fb:app_id | 1401488693436528 |
| apple-itunes-app | app-id=1477376905, app-argument=https://github.com/_view_fragments/issues/show/feast-dev/feast/5652/issue_layout |
| twitter:image | https://opengraph.githubassets.com/b588130a7a3b909bb1989459036c185ab801bd3edb59cd6ee057376826a4a062/feast-dev/feast/issues/5652 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/b588130a7a3b909bb1989459036c185ab801bd3edb59cd6ee057376826a4a062/feast-dev/feast/issues/5652 |
| og:image:alt | Is your feature request related to a problem? Please describe. A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] Hello everyone, I have a question about t... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | haoxu0 |
| hostname | github.com |
| expected-hostname | github.com |
| None | b3c0f155eafc27e60db6e254d1ffff0e072e9ab3b4018a5ee518797c19d89f86 |
| turbo-cache-control | no-preview |
| go-import | github.com/feast-dev/feast git https://github.com/feast-dev/feast.git |
| octolytics-dimension-user_id | 57027613 |
| octolytics-dimension-user_login | feast-dev |
| octolytics-dimension-repository_id | 161133770 |
| octolytics-dimension-repository_nwo | feast-dev/feast |
| octolytics-dimension-repository_public | true |
| octolytics-dimension-repository_is_fork | false |
| octolytics-dimension-repository_network_root_id | 161133770 |
| octolytics-dimension-repository_network_root_nwo | feast-dev/feast |
| turbo-body-classes | logged-out env-production page-responsive |
| disable-turbo | false |
| browser-stats-url | https://api.github.com/_private/browser/stats |
| browser-errors-url | https://api.github.com/_private/browser/errors |
| release | 4a10310af51a1bfffbedc4fd81cb582acf0cb0ff |
| ui-target | full |
| theme-color | #1e2327 |
| color-scheme | light dark |
| react-app-name | issues |
Links:
Viewport: width=device-width