Skip to content

Update serving endpoint served entity limit in docs #1530

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.

Sign up for GitHub

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

Open
divya0709 wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update serving endpoint served entity limit in docs #1530

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion databricks/sdk/service/serving.py
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

2 changes: 1 addition & 1 deletion docs/workspace/serving/serving_endpoints.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@
Endpoints expose the underlying models as scalable REST API endpoints using serverless compute. This means
the endpoints and associated compute resources are fully managed by Databricks and will not appear in your
cloud account. A serving endpoint can consist of one or more MLflow models from the Databricks Model
Registry, called served entities. A serving endpoint can have at most ten served entities. You can
Registry, called served entities. A serving endpoint can have at most 15 served entities. You can
configure traffic settings to define how requests should be routed to your served entities behind an
endpoint. Additionally, you can configure the scale of resources that should be applied to each served
entity.
Expand Down
Loading