Skip to content
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

[Feature]: Support for ML Feature Store and Model Registry #3341

Open
1 task
emuriithi21 opened this issue Jan 17, 2025 · 1 comment
Open
1 task

[Feature]: Support for ML Feature Store and Model Registry #3341

emuriithi21 opened this issue Jan 17, 2025 · 1 comment
Labels
feature-request Used to mark issues with provider's missing functionalities

Comments

@emuriithi21
Copy link

Company Name

Snowflake

Use Cases or Problem Statement

Support snowflake feature store for mlops

Category

category:resource

Object type(s)

No response

Proposal

No response

How much impact is this issue causing?

Low

Additional Information

No response

Would you like to implement a fix?

  • Yeah, I'll take it 😎
@emuriithi21 emuriithi21 added the feature-request Used to mark issues with provider's missing functionalities label Jan 17, 2025
@emuriithi21 emuriithi21 changed the title [Feature]: [Feature]: Support for ML Feature Store and Model Registry Jan 17, 2025
@sfc-gh-jcieslak
Copy link
Collaborator

Hello @emuriithi21 👋
Could you please elaborate a bit on the requested features? To implement a given feature, we need to have control over the thing object (create, alter, show / desc, drop) through SQL. With Model Registry, I'm guessing you are referring to this feature (?), but I'm not sure how could we implement ML Feature Store. It seems like it can be communicated over the Python connector. If that is the case we wouldn't be able to implement it, as mentions, we are using SQL to communicate with Snowflake.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request Used to mark issues with provider's missing functionalities
Projects
None yet
Development

No branches or pull requests

2 participants