Repository navigation
docs: Use the supported Snowflake selector in federation examples - #6974
Open
Hanabi9249 wants to merge 1 commit into
Open
Hanabi9249 wants to merge 1 commit into
Hanabi9249 wants to merge 1 commit into
Conversation
Signed-off-by: Hanabi <3666353208@qq.com>
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The federation guide's four complete platform/team feature_store.yaml examples use offline_store.type: snowflake. SnowflakeOfflineStoreConfig declares the selector as snowflake.offline, and the current offline-store routing table uses that same selector.
Update only the four YAML selectors to snowflake.offline. All database, warehouse, account and schema values remain as shown in the examples.
Validation: exact unchanged FeastConfigBaseModel and SnowflakeOfflineStoreConfig source bodies, isolated with real installed Pydantic 2.12.5 and PyYAML 6.0.3. The baseline produced 18 passing cases and four literal_error failures on these public examples; the patched tree passed the same 22 cases (10 public configuration schema inputs and 12 controls). git diff --cached --check passed.
Full Feast/RepoConfig integration, dynamic imports, CLI execution, Snowflake connector/accounts/databases and operator runtime were not run.