<?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>idea Re: Ability for Compose to start a databricks cluster prior to scheduled run - Status changed to: Closed - Declined in Suggest an Idea</title>
    <link>https://community.qlik.com/t5/Suggest-an-Idea/Ability-for-Compose-to-start-a-databricks-cluster-prior-to/idc-p/1882497#M8499</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.qlik.com/t5/user/viewprofilepage/user-id/113972"&gt;@lpmarino&lt;/a&gt;&amp;nbsp; - I'm closing this request because this ability is already supported via databricks clusters starting up on connection attempts and retry mechanisms in Compose.&amp;nbsp;&lt;/P&gt;&lt;P&gt;If you have a databricks cluster shutdown and start a Qlik Compose job - the job connecting to databricks will auto-start the cluster.&amp;nbsp; While the cluster startup may cause a timeout in Compose (typically it won't) , the ability to&amp;nbsp; configure RETRY in Compose supports retrying the timed-out operation.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have tested this in an environment and kicking off the Compose job will auto-start the databricks cluster.&lt;/P&gt;&lt;P&gt;If I have mis-understood the request at all , please comment.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Retry can be found un the project settings and "Environment" tab -&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="TimGarrod_0-1642540702350.png" style="width: 400px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/70459iE8CA924FBC3413F5/image-size/medium?v=v2&amp;amp;px=400" role="button" title="TimGarrod_0-1642540702350.png" alt="TimGarrod_0-1642540702350.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 18 Jan 2022 21:18:29 GMT</pubDate>
    <dc:creator>TimGarrod</dc:creator>
    <dc:date>2022-01-18T21:18:29Z</dc:date>
    <item>
      <title>Re: Ability for Compose to start a databricks cluster prior to scheduled run - Status changed to: Closed - Declined</title>
      <link>https://community.qlik.com/t5/Suggest-an-Idea/Ability-for-Compose-to-start-a-databricks-cluster-prior-to/idc-p/1882497#M8499</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.qlik.com/t5/user/viewprofilepage/user-id/113972"&gt;@lpmarino&lt;/a&gt;&amp;nbsp; - I'm closing this request because this ability is already supported via databricks clusters starting up on connection attempts and retry mechanisms in Compose.&amp;nbsp;&lt;/P&gt;&lt;P&gt;If you have a databricks cluster shutdown and start a Qlik Compose job - the job connecting to databricks will auto-start the cluster.&amp;nbsp; While the cluster startup may cause a timeout in Compose (typically it won't) , the ability to&amp;nbsp; configure RETRY in Compose supports retrying the timed-out operation.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have tested this in an environment and kicking off the Compose job will auto-start the databricks cluster.&lt;/P&gt;&lt;P&gt;If I have mis-understood the request at all , please comment.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Retry can be found un the project settings and "Environment" tab -&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="TimGarrod_0-1642540702350.png" style="width: 400px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/70459iE8CA924FBC3413F5/image-size/medium?v=v2&amp;amp;px=400" role="button" title="TimGarrod_0-1642540702350.png" alt="TimGarrod_0-1642540702350.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 18 Jan 2022 21:18:29 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Suggest-an-Idea/Ability-for-Compose-to-start-a-databricks-cluster-prior-to/idc-p/1882497#M8499</guid>
      <dc:creator>TimGarrod</dc:creator>
      <dc:date>2022-01-18T21:18:29Z</dc:date>
    </item>
    <item>
      <title>Re: Ability for Compose to start a databricks cluster prior to scheduled run - Status changed to: Closed - Already Available</title>
      <link>https://community.qlik.com/t5/Suggest-an-Idea/Ability-for-Compose-to-start-a-databricks-cluster-prior-to/idc-p/1882498#M8500</link>
      <description />
      <pubDate>Tue, 18 Jan 2022 21:19:41 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Suggest-an-Idea/Ability-for-Compose-to-start-a-databricks-cluster-prior-to/idc-p/1882498#M8500</guid>
      <dc:creator>TimGarrod</dc:creator>
      <dc:date>2022-01-18T21:19:41Z</dc:date>
    </item>
  </channel>
</rss>

