<?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 Changes in Databricks rest api in Administration &amp; Architecture</title>
    <link>https://community.databricks.com/t5/administration-architecture/changes-in-databricks-rest-api/m-p/89755#M1782</link>
    <description>&lt;P&gt;Hi all,&amp;nbsp;&lt;BR /&gt;Just wanted to ask if there is an announcement regarding changes on Databricks REST API?&amp;nbsp;&amp;nbsp;&lt;BR /&gt;Because I had weird experiences in using the REST API.&amp;nbsp;&lt;BR /&gt;Specifically for Query History API&amp;nbsp;&lt;/P&gt;&lt;P&gt;Last Aug 29, 2024.&amp;nbsp;&lt;BR /&gt;I created a script to pull get request in the endpoint. I saw a key in the response named:&amp;nbsp;&lt;/P&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;&lt;SPAN&gt;'query_source': {'driver_info': {'driver_name': '', 'version_number': '2.0', etc..'},&lt;BR /&gt;&lt;BR /&gt;I can get all the response but not with that specific key. (use case is to determine where it is used ex:NB, Genie space, etc.)&amp;nbsp;&lt;BR /&gt;I checked the query params, but there is nothing related to query_source. I even also enabled metrics, still no luck.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;But then with my playful mind, I added this on my parameters:&amp;nbsp;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;"include_query_source"&lt;/SPAN&gt;&lt;SPAN&gt;: &lt;/SPAN&gt;&lt;SPAN&gt;'true'&lt;/SPAN&gt;&lt;SPAN&gt;, - which is not part of the documentation - and you guess it, it worked.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;SPAN&gt;Now as I am writing this, the 'query_source' is now missing in the response sample in the documentation. But still works.&amp;nbsp;&lt;BR /&gt;It is better if we have and announcement regarding the changes of the endpoints because this might cause issues in the future when we decide to create a workflow for this kind of use case.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/DIV&gt;&lt;/DIV&gt;</description>
    <pubDate>Fri, 13 Sep 2024 10:00:49 GMT</pubDate>
    <dc:creator>Databrixer</dc:creator>
    <dc:date>2024-09-13T10:00:49Z</dc:date>
    <item>
      <title>Changes in Databricks rest api</title>
      <link>https://community.databricks.com/t5/administration-architecture/changes-in-databricks-rest-api/m-p/89755#M1782</link>
      <description>&lt;P&gt;Hi all,&amp;nbsp;&lt;BR /&gt;Just wanted to ask if there is an announcement regarding changes on Databricks REST API?&amp;nbsp;&amp;nbsp;&lt;BR /&gt;Because I had weird experiences in using the REST API.&amp;nbsp;&lt;BR /&gt;Specifically for Query History API&amp;nbsp;&lt;/P&gt;&lt;P&gt;Last Aug 29, 2024.&amp;nbsp;&lt;BR /&gt;I created a script to pull get request in the endpoint. I saw a key in the response named:&amp;nbsp;&lt;/P&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;&lt;SPAN&gt;'query_source': {'driver_info': {'driver_name': '', 'version_number': '2.0', etc..'},&lt;BR /&gt;&lt;BR /&gt;I can get all the response but not with that specific key. (use case is to determine where it is used ex:NB, Genie space, etc.)&amp;nbsp;&lt;BR /&gt;I checked the query params, but there is nothing related to query_source. I even also enabled metrics, still no luck.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;But then with my playful mind, I added this on my parameters:&amp;nbsp;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;"include_query_source"&lt;/SPAN&gt;&lt;SPAN&gt;: &lt;/SPAN&gt;&lt;SPAN&gt;'true'&lt;/SPAN&gt;&lt;SPAN&gt;, - which is not part of the documentation - and you guess it, it worked.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;SPAN&gt;Now as I am writing this, the 'query_source' is now missing in the response sample in the documentation. But still works.&amp;nbsp;&lt;BR /&gt;It is better if we have and announcement regarding the changes of the endpoints because this might cause issues in the future when we decide to create a workflow for this kind of use case.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/DIV&gt;&lt;/DIV&gt;</description>
      <pubDate>Fri, 13 Sep 2024 10:00:49 GMT</pubDate>
      <guid>https://community.databricks.com/t5/administration-architecture/changes-in-databricks-rest-api/m-p/89755#M1782</guid>
      <dc:creator>Databrixer</dc:creator>
      <dc:date>2024-09-13T10:00:49Z</dc:date>
    </item>
    <item>
      <title>Re: Changes in Databricks rest api</title>
      <link>https://community.databricks.com/t5/administration-architecture/changes-in-databricks-rest-api/m-p/89775#M1787</link>
      <description>&lt;P&gt;Yeah, totally agree with you. It should be documented/mentioned somewhere. Or maybe the API should be versioned, so if they introduce a new version, it won't break existing workflows.&lt;BR /&gt;Anyway, thanks for sharing!&lt;/P&gt;</description>
      <pubDate>Fri, 13 Sep 2024 11:10:45 GMT</pubDate>
      <guid>https://community.databricks.com/t5/administration-architecture/changes-in-databricks-rest-api/m-p/89775#M1787</guid>
      <dc:creator>szymon_dybczak</dc:creator>
      <dc:date>2024-09-13T11:10:45Z</dc:date>
    </item>
    <item>
      <title>Re: Changes in Databricks rest api</title>
      <link>https://community.databricks.com/t5/administration-architecture/changes-in-databricks-rest-api/m-p/89776#M1788</link>
      <description>&lt;P&gt;Agree. They have announcements on other endpoints in the documentation but it is better to have a dedicated page for the list of versions.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 13 Sep 2024 11:23:27 GMT</pubDate>
      <guid>https://community.databricks.com/t5/administration-architecture/changes-in-databricks-rest-api/m-p/89776#M1788</guid>
      <dc:creator>Databrixer</dc:creator>
      <dc:date>2024-09-13T11:23:27Z</dc:date>
    </item>
  </channel>
</rss>

