-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Comparing changes
Open a pull request
base repository: feast-dev/feast
base: 863b09f
head repository: feast-dev/feast
compare: ddb2e9a
- 6 commits
- 66 files changed
- 4 contributors
Commits on Jul 20, 2026
-
ci: Preserve OpenLineage placeholder allowlist (#6619)
Signed-off-by: Francisco Javier Arceo <farceo@redhat.com>
Configuration menu - View commit details
-
Copy full SHA for 294efad - Browse repository at this point
Copy the full SHA 294efadView commit details
Commits on Jul 22, 2026
-
feat: Making feast vector store with open ai search api compatible (#…
…6121) * Phase 1: Added basic open ai competible search api in the vector store Signed-off-by: Chaitany patel <patelchaitany93@gmail.com> * Added test for testing the new OpenAI api Signed-off-by: Chaitany patel <patelchaitany93@gmail.com> * fix: patch fastapi_mcp circular recursion that blocks MCP endpoint registration fastapi_mcp 0.4.0 resolve_schema_references() has no cycle detection. Feast's OpenAPI schema contains self-referential protobuf types (Value -> Struct -> Value) which trigger a RecursionError. The error is silently caught, so the /mcp route never gets registered and CI gets a 404. Add _resolve_schema_references_safe() that tracks a seen-refs set to break circular chains, and monkey-patch it into fastapi_mcp before FastApiMCP processes the schema. Non-circular schemas produce identical output to the original. Signed-off-by: Chaitany patel <patelchaitany93@gmail.com> * docs: Update filtering requirements for Postgres and SQLite backends in alpha-vector-database.md; enhance error handling in feature_server.py for invalid requests; clarify unsupported parameters in feature_store.py; ensure requested_features is a list in remote.py Signed-off-by: Chaitany patel <patelchaitany93@gmail.com> Signed-off-by: Chaitany Patel <patelchaitany93@gmail.com> * - Accept rewrite_query=false as a no-op; only reject true - Document score conversion formulas and distance metrics in alpha-vector-database.md - Add Sentence Transformers as a supported embedding provider - Fix embedding_model config example in docstring Signed-off-by: Chaitany Patel <patelchaitany93@gmail.com> * - Add GET /v1/vector_stores and GET /v1/vector_stores/{id} endpoints with RBAC enforcement (DESCRIBE permission) - Introduce VectorStoreRegistry cache that derives vs_{sha256} IDs from project + feature view name, refreshed on registry TTL cycle - Replace raw feature view names with stable vs_ identifiers in search responses (file_id, filename fields) - Update docs, blog post, and integration tests for new ID scheme - Add unit tests for VectorStoreRegistry, ID generation, and object building Signed-off-by: Chaitany Patel <patelchaitany93@gmail.com> * Remove LiteLLM embedding provider, default to Sentence Transformers Signed-off-by: Chaitany Patel <patelchaitany93@gmail.com> * Updatethe Docs, documented OpenAI search API as Alpha Signed-off-by: Chaitany Patel <patelchaitany93@gmail.com> --------- Signed-off-by: Chaitany patel <patelchaitany93@gmail.com> Signed-off-by: Chaitany Patel <patelchaitany93@gmail.com>
Configuration menu - View commit details
-
Copy full SHA for 54da19a - Browse repository at this point
Copy the full SHA 54da19aView commit details
Commits on Jul 23, 2026
-
docs: Fix dead Slack invite link (#6632)
* docs: Fix dead Slack invite link The "Come say hi on Slack!" link pointed at communityinviter.com, which has been deprecated; the invite no longer resolves. Repoint it at the https://slack.feast.dev/ vanity URL, which redirects to the current Feast Slack workspace invite and stays valid as the underlying invite rotates. Updated in both the README and docs/community.md (the source for the docs.feast.dev/community page). Signed-off-by: Larry Singleton <166439969+larrysingleton007@users.noreply.github.com> * docs: Update Slack link in README template README.md is auto-generated from infra/templates/README.md.jinja2, so the source template needs the same fix. Update it and regenerate; README.md is unchanged since it already carried the corrected link. This also resolves the template-consistency check that was failing on the direct README edit. Signed-off-by: Larry Singleton <166439969+larrysingleton007@users.noreply.github.com> --------- Signed-off-by: Larry Singleton <166439969+larrysingleton007@users.noreply.github.com>
Configuration menu - View commit details
-
Copy full SHA for 955403e - Browse repository at this point
Copy the full SHA 955403eView commit details -
feat: Added optional namespace/colleciton to datasets
Signed-off-by: ntkathole <nikhilkathole2683@gmail.com>
Configuration menu - View commit details
-
Copy full SHA for 165fcf2 - Browse repository at this point
Copy the full SHA 165fcf2View commit details -
feat: Updated datasets UI to support grouping
Signed-off-by: ntkathole <nikhilkathole2683@gmail.com>
Configuration menu - View commit details
-
Copy full SHA for 7ae64ec - Browse repository at this point
Copy the full SHA 7ae64ecView commit details -
fix: Avoid importing feast.feature_store at mcp_server import time
mcp_server used a module-level `from feast.feature_store import FeatureStore` solely for a type annotation on add_mcp_support_to_app. Because the feast.infra.mcp_servers package __init__ eagerly imports mcp_server, importing the package pulled in the entire feature_store import graph. Under parallel unit-test collection (pytest -n) this intermittently raced with an in-progress feature_store import and failed collection of test_mcp_server.py with `KeyError: 'feast.infra.mcp_servers.mcp_server'`. Move the import under TYPE_CHECKING and use a forward reference, so importing mcp_server no longer triggers the feature_store graph. Public API and the annotation are unchanged. Signed-off-by: Larry Singleton <166439969+larrysingleton007@users.noreply.github.com>
Configuration menu - View commit details
-
Copy full SHA for ddb2e9a - Browse repository at this point
Copy the full SHA ddb2e9aView commit details
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff 863b09f...ddb2e9a