<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: databricks-vectorsearch 0.53 unable to use similarity_search() in Machine Learning</title>
    <link>https://community.databricks.com/t5/machine-learning/databricks-vectorsearch-0-53-unable-to-use-similarity-search/m-p/136432#M4380</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/154641"&gt;@snaveedgm&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P&gt;This is interesting - can you double-check that the service principal has &lt;STRONG&gt;CAN QUERY&lt;/STRONG&gt; on the embedding endpoint used for ingestion and/or querying (databricks-bge-large-en in your case)? Even though your direct REST test works, double-check permissions are consistent across workspaces/endpoints if you have multi-workspace setups.&lt;/P&gt;
&lt;P class="qt3gz91 paragraph"&gt;Given your environment and error, the fastest unblock is either PAT or query_vector:&lt;/P&gt;
&lt;DIV class="go8b9g1 _7pq7t6cd" data-ui-element="code-block-container"&gt;&lt;LI-CODE lang="python"&gt;from databricks.vector_search.client import VectorSearchClient

# Use PAT (set DATABRICKS_TOKEN in the environment or pass personal_access_token)
vsc = VectorSearchClient(
workspace_url=workspace_url,
personal_access_token=os.environ["DATABRICKS_TOKEN"] # or pass the token directly
)

index = vsc.get_index(endpoint_name=endpoint_name, index_name=index_name)
&lt;/LI-CODE&gt;&lt;/DIV&gt;</description>
    <pubDate>Tue, 28 Oct 2025 15:58:31 GMT</pubDate>
    <dc:creator>stbjelcevic</dc:creator>
    <dc:date>2025-10-28T15:58:31Z</dc:date>
    <item>
      <title>databricks-vectorsearch 0.53 unable to use similarity_search()</title>
      <link>https://community.databricks.com/t5/machine-learning/databricks-vectorsearch-0-53-unable-to-use-similarity-search/m-p/113320#M3998</link>
      <description>&lt;P&gt;I have an issue with &lt;STRONG&gt;databricks-vectorsearch &lt;/STRONG&gt;package. Version 0.51 suddenly stopped working this week because:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;It now expected me to provide azure_tenant_id in addition to service principal's client ID and secret.&lt;/LI&gt;&lt;LI&gt;After supplying tenant ID, it showed some bug like "Unsupported Types" time.time() + oauth_token_data["expires_in"].&lt;/LI&gt;&lt;LI&gt;I then upgraded to 0.53 and this bug was resolved and some functions like get_index() started working. However, now the similarity_search() function gives:&lt;/LI&gt;&lt;UL&gt;&lt;LI&gt;&lt;STRONG&gt;b'{"error_code":"PERMISSION_DENIED","message":"Failed to call Model Serving endpoint: databricks-bge-large-en."}', status_code 403&lt;/STRONG&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;LI&gt;I have tried querying the &lt;STRONG&gt;databricks-bge-large-en&lt;/STRONG&gt; &amp;nbsp;endpoint separately via REST for my service account and it works fine, so the issue seems specific to this package.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Please advise.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Code Snippet:&lt;/P&gt;&lt;P&gt;from databricks.vector_search.client import VectorSearchClient&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;vsc = VectorSearchClient(&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp; workspace_url=workspace_url,&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp; service_principal_client_id=sp_client_id,&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp; service_principal_client_secret=sp_client_secret,&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp; azure_tenant_id=tenant_id&lt;/P&gt;&lt;P&gt;)&lt;/P&gt;&lt;P&gt;index = vsc.get_index(endpoint_name=endpoint_name, index_name=index_name)&lt;/P&gt;&lt;P&gt;index.similarity_search(num_results=3, columns=["chunked_text"], query_text="example_query")&lt;/P&gt;</description>
      <pubDate>Fri, 21 Mar 2025 16:25:07 GMT</pubDate>
      <guid>https://community.databricks.com/t5/machine-learning/databricks-vectorsearch-0-53-unable-to-use-similarity-search/m-p/113320#M3998</guid>
      <dc:creator>snaveedgm</dc:creator>
      <dc:date>2025-03-21T16:25:07Z</dc:date>
    </item>
    <item>
      <title>Re: databricks-vectorsearch 0.53 unable to use similarity_search()</title>
      <link>https://community.databricks.com/t5/machine-learning/databricks-vectorsearch-0-53-unable-to-use-similarity-search/m-p/136432#M4380</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/154641"&gt;@snaveedgm&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P&gt;This is interesting - can you double-check that the service principal has &lt;STRONG&gt;CAN QUERY&lt;/STRONG&gt; on the embedding endpoint used for ingestion and/or querying (databricks-bge-large-en in your case)? Even though your direct REST test works, double-check permissions are consistent across workspaces/endpoints if you have multi-workspace setups.&lt;/P&gt;
&lt;P class="qt3gz91 paragraph"&gt;Given your environment and error, the fastest unblock is either PAT or query_vector:&lt;/P&gt;
&lt;DIV class="go8b9g1 _7pq7t6cd" data-ui-element="code-block-container"&gt;&lt;LI-CODE lang="python"&gt;from databricks.vector_search.client import VectorSearchClient

# Use PAT (set DATABRICKS_TOKEN in the environment or pass personal_access_token)
vsc = VectorSearchClient(
workspace_url=workspace_url,
personal_access_token=os.environ["DATABRICKS_TOKEN"] # or pass the token directly
)

index = vsc.get_index(endpoint_name=endpoint_name, index_name=index_name)
&lt;/LI-CODE&gt;&lt;/DIV&gt;</description>
      <pubDate>Tue, 28 Oct 2025 15:58:31 GMT</pubDate>
      <guid>https://community.databricks.com/t5/machine-learning/databricks-vectorsearch-0-53-unable-to-use-similarity-search/m-p/136432#M4380</guid>
      <dc:creator>stbjelcevic</dc:creator>
      <dc:date>2025-10-28T15:58:31Z</dc:date>
    </item>
  </channel>
</rss>

