Skip to content

agent-langgraph[-advanced]: pin databricks-ai-bridge to PR #435 (temporary)#235

Open
jennsun wants to merge 1 commit into
databricks:mainfrom
jennsun:jennsun/test-vector-search-index-import-fix
Open

agent-langgraph[-advanced]: pin databricks-ai-bridge to PR #435 (temporary)#235
jennsun wants to merge 1 commit into
databricks:mainfrom
jennsun:jennsun/test-vector-search-index-import-fix

Conversation

@jennsun

@jennsun jennsun commented Jun 8, 2026

Copy link
Copy Markdown
Contributor

Summary

Temporary pin so the agent-langgraph and agent-langgraph-advanced templates boot on environments where the underlying vector-search package has stopped re-exporting VectorSearchIndex from databricks.vector_search.client.

Companion to databricks/databricks-ai-bridge#435.

Why

Users hit ImportError: cannot import name 'VectorSearchIndex' from 'databricks.vector_search.client' on agent boot. Root cause is in databricks_openai.vector_search_retriever_tool, which databricks_langchain pulls in transitively. PR #435 in databricks-ai-bridge fixes the import; this change pins both templates to that PR's branch via [tool.uv.sources] so customers aren't blocked while the bridge release goes out.

Changes

Both agent-langgraph/pyproject.toml and agent-langgraph-advanced/pyproject.toml:

  • Add databricks-openai (and, for plain agent-langgraph, databricks-ai-bridge) as direct deps so [tool.uv.sources] can override them.
  • [tool.uv.sources] block pointing databricks-ai-bridge, databricks-openai, databricks-langchain at the fix branch in databricks/databricks-ai-bridge.

Test plan

  • uv sync resolves all three packages from commit 131252d6 of the fix branch (verified locally).
  • from databricks_langchain import ChatDatabricks, DatabricksMCPServer, DatabricksMultiServerMCPClient (the template's own import) succeeds.
  • Reproduced user's exact ImportError by stripping the side-effect re-export from the installed databricks.vector_search.client, then confirmed the template's import chain still succeeds against the fixed databricks_openai.
  • After PR #435 merges + the next databricks-ai-bridge release ships, revert this PR (remove [tool.uv.sources] and the extra direct-dep entries).

Reverting

# Delete the [tool.uv.sources] block and the databricks-openai (and
# databricks-ai-bridge in plain agent-langgraph) entries from dependencies.

…emporary)

Pins databricks-ai-bridge, databricks-openai, and databricks-langchain
to databricks/databricks-ai-bridge#435 so the LangGraph templates boot
on environments that pull a databricks-vectorsearch / databricks-ai-
search version that no longer re-exports VectorSearchIndex from
databricks.vector_search.client.

The legacy import in databricks_openai was the trigger:
  ImportError: cannot import name 'VectorSearchIndex' from
  'databricks.vector_search.client'

Remove this override once a databricks-ai-bridge release containing the
fix is published to PyPI.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant