-
Notifications
You must be signed in to change notification settings - Fork 4k
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
Add Clarifai as a provider in MLflow Deployments Server #10642
base: master
Are you sure you want to change the base?
Conversation
Signed-off-by: Sai Nivedh <sainivedh123@gmail.com>
Documentation preview for e9791ab will be available here when this CircleCI job completes successfully. More info
|
Signed-off-by: Sai Nivedh <sainivedh123@gmail.com>
@BenWilson2 Could you please review when you have a moment? |
Hi @sainivedh the gateway has been deprecated. Could you add the implementation here instead of the deprecated namespace? |
@BenWilson2, I have opened this pull request to update to the latest version of the Deployment Server. I've included examples here. mlflow deployments start-server --config-path examples/deployments/deployments_server/clarifai/config.yaml --port 7000 |
You added implementations to |
@BenWilson2, I appreciate your suggestions, but I'm a bit uncertain about your point. The deployments server utilizes get_provider from |
LOL sorry, it's been a long week. I'll take a look at the PR now ;) |
# Embeddings request | ||
response_embeddings = client.predict( | ||
endpoint="embeddings", | ||
inputs={"input": ["Do you carry the Storm Trooper costume in size 2T?"]}, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
haha great example
Hi @sainivedh when you push the changes, can you rebase on master as well just to make sure that you have the latest CI config? |
Co-authored-by: Ben Wilson <39283302+BenWilson2@users.noreply.github.com> Signed-off-by: Sai Nivedh <sainivedh123@gmail.com>
Co-authored-by: Ben Wilson <39283302+BenWilson2@users.noreply.github.com> Signed-off-by: Sai Nivedh <sainivedh123@gmail.com>
Co-authored-by: Ben Wilson <39283302+BenWilson2@users.noreply.github.com> Signed-off-by: Sai Nivedh <sainivedh123@gmail.com>
Co-authored-by: Ben Wilson <39283302+BenWilson2@users.noreply.github.com> Signed-off-by: Sai Nivedh <sainivedh123@gmail.com>
Co-authored-by: Ben Wilson <39283302+BenWilson2@users.noreply.github.com> Signed-off-by: Sai Nivedh <sainivedh123@gmail.com>
Signed-off-by: Sai Nivedh <sainivedh123@gmail.com>
Signed-off-by: Sai Nivedh <sainivedh123@gmail.com>
Signed-off-by: Sai Nivedh <sainivedh123@gmail.com>
Signed-off-by: Sai Nivedh <sainivedh123@gmail.com>
Hello @BenWilson2, I've pushed the changes. Kindly take a look when you get a chance. |
Hello @BenWilson2, Could you please review when you have a moment? |
Related Issues/PRs
Add Clarifai as a provider in MLflow Deployments Server
What changes are proposed in this pull request?
How is this PR tested?
Does this PR require documentation update?
Release Notes
Is this a user-facing change?
What component(s), interfaces, languages, and integrations does this PR affect?
Components
area/artifacts
: Artifact stores and artifact loggingarea/build
: Build and test infrastructure for MLflowarea/docs
: MLflow documentation pagesarea/examples
: Example codearea/gateway
: AI Gateway service, Gateway client APIs, third-party Gateway integrationsarea/model-registry
: Model Registry service, APIs, and the fluent client calls for Model Registryarea/models
: MLmodel format, model serialization/deserialization, flavorsarea/recipes
: Recipes, Recipe APIs, Recipe configs, Recipe Templatesarea/projects
: MLproject format, project running backendsarea/scoring
: MLflow Model server, model deployment tools, Spark UDFsarea/server-infra
: MLflow Tracking server backendarea/tracking
: Tracking Service, tracking client APIs, autologgingInterface
area/uiux
: Front-end, user experience, plotting, JavaScript, JavaScript dev serverarea/docker
: Docker use across MLflow's components, such as MLflow Projects and MLflow Modelsarea/sqlalchemy
: Use of SQLAlchemy in the Tracking Service or Model Registryarea/windows
: Windows supportLanguage
language/r
: R APIs and clientslanguage/java
: Java APIs and clientslanguage/new
: Proposals for new client languagesIntegrations
integrations/azure
: Azure and Azure ML integrationsintegrations/sagemaker
: SageMaker integrationsintegrations/databricks
: Databricks integrationsHow should the PR be classified in the release notes? Choose one:
rn/none
- No description will be included. The PR will be mentioned only by the PR number in the "Small Bugfixes and Documentation Updates" sectionrn/breaking-change
- The PR will be mentioned in the "Breaking Changes" sectionrn/feature
- A new user-facing feature worth mentioning in the release notesrn/bug-fix
- A user-facing bug fix worth mentioning in the release notesrn/documentation
- A user-facing documentation change worth mentioning in the release notes