<?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 Restricting Spark Connect Behind Premium Plan Paywall? in Administration &amp; Architecture</title>
    <link>https://community.databricks.com/t5/administration-architecture/restricting-spark-connect-behind-premium-plan-paywall/m-p/46333#M433</link>
    <description>&lt;P&gt;Quoting the &lt;A href="https://learn.microsoft.com/en-us/azure/databricks/dev-tools/databricks-connect-ref" target="_self"&gt;databricks-connect docs&lt;/A&gt;, "&lt;SPAN&gt;For Databricks Runtime 13.0 and above, Databricks Connect is now built on open-source Spark Connect." What is odd to me is that a requirement for utilizing this open source Spark feature on Databricks, is Unity Catalog, which requires a premium Databricks plan.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;I would understand if this was a restriction in databricks-connect proper, that power-users could bypass by simply using the native Spark Connect, but using Spark Connect directly to connect to a cluster outside of a Unity enabled workspace also does not work.&lt;/P&gt;&lt;P&gt;What is this reasoning for this restriction other than pushing users onto premium plans? Eventually non-premium/Unity users will not be able to use any form of databricks-connect once Databricks Runtime 12 is discontinued. Is there any plan for addressing this restriction?&lt;/P&gt;</description>
    <pubDate>Tue, 26 Sep 2023 21:13:39 GMT</pubDate>
    <dc:creator>gandersen-codes</dc:creator>
    <dc:date>2023-09-26T21:13:39Z</dc:date>
    <item>
      <title>Restricting Spark Connect Behind Premium Plan Paywall?</title>
      <link>https://community.databricks.com/t5/administration-architecture/restricting-spark-connect-behind-premium-plan-paywall/m-p/46333#M433</link>
      <description>&lt;P&gt;Quoting the &lt;A href="https://learn.microsoft.com/en-us/azure/databricks/dev-tools/databricks-connect-ref" target="_self"&gt;databricks-connect docs&lt;/A&gt;, "&lt;SPAN&gt;For Databricks Runtime 13.0 and above, Databricks Connect is now built on open-source Spark Connect." What is odd to me is that a requirement for utilizing this open source Spark feature on Databricks, is Unity Catalog, which requires a premium Databricks plan.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;I would understand if this was a restriction in databricks-connect proper, that power-users could bypass by simply using the native Spark Connect, but using Spark Connect directly to connect to a cluster outside of a Unity enabled workspace also does not work.&lt;/P&gt;&lt;P&gt;What is this reasoning for this restriction other than pushing users onto premium plans? Eventually non-premium/Unity users will not be able to use any form of databricks-connect once Databricks Runtime 12 is discontinued. Is there any plan for addressing this restriction?&lt;/P&gt;</description>
      <pubDate>Tue, 26 Sep 2023 21:13:39 GMT</pubDate>
      <guid>https://community.databricks.com/t5/administration-architecture/restricting-spark-connect-behind-premium-plan-paywall/m-p/46333#M433</guid>
      <dc:creator>gandersen-codes</dc:creator>
      <dc:date>2023-09-26T21:13:39Z</dc:date>
    </item>
  </channel>
</rss>

