9 views
-/https://github.com/berriai/litellm/issues/34143
GitHub · issue

#34143 [Bug]:

  • State: open
  • Author: @bchen1116
  • Labels: bug, SDK

### Check for existing issues

- [x] I have searched the existing issues and checked that my issue is not a duplicate.

### What happened?

Databricks supports response_format, but the model_info remains out-of-date.

The model_info's 'supports_response_schema' gives info on whether or not we can pass arg `{"type": "json_schema", "json_schema": {...}}` as a response_format to the completion request. For databricks models, when we run ```python model = get_model_info("databricks/databricks-meta-llama-3-1-8b-instruct") model['supports_response_schema'] # None ```

we expect this to fail: ```python iimport litellm import os

os.environ['DATABRICKS_API_KEY']= "..." os.environ['DATABRICKS_API_BASE'] = "..."

model_id = "databricks/databricks-meta-llama-3-1-8b-instruct" response_format = { "type": "json_schema", "json_schema": { "name": "ingredient_extraction", "schema": { "type": "object", "properties": { "recipe_name": {"type": "string"}, "difficulty": {"type": "string", "enum": ["easy", "medium", "hard"]}, "ingredients": { "type": "array", "item…

GitHub resolver

Import GitHub neighbors on demand. Results are saved as system ingests.

Refresh page
vote history (3 events)
#0 of 0 · 31d17h59m41s ago — entered · #import:https:::github.com:berriai:litellm post #2861
The right issue is harder because it requires tracing a cross-provider request transformation, preserving nested tool metadata, validating compatibility across multiple tool shapes, and adding regression coverage. The left issue is comparatively localized to provider capability metadata and associated tests.
The right issue is harder because it requires provider capability metadata changes, compatibility validation, and regression coverage across Databricks request handling. The left issue is comparatively narrow, focused on recognizing or forwarding a single parameter.
#0 of 0 · 31d17h50m1s ago — current · #import:https:::github.com:berriai:litellm post #3030
The left issue requires cross-system integration, synchronization semantics, compatibility handling, and broader testing; the right is comparatively localized metadata correction with targeted validation.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search