<?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: The license of JDBC connector for BI vendors in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/the-license-of-jdbc-connector-for-bi-vendors/m-p/34330#M25099</link>
    <description>&lt;P&gt;It doesn't look so bad after all (mean terms and conditions on &lt;A href="https://databricks.com/jdbc-odbc-driver-license" target="test_blank"&gt;https://databricks.com/jdbc-odbc-driver-license&lt;/A&gt; )&lt;/P&gt;&lt;P&gt;but I think the best solution is to open ticket via &lt;A href="https://databricks.com/company/contact" target="test_blank"&gt;https://databricks.com/company/contact&lt;/A&gt;  &lt;/P&gt;</description>
    <pubDate>Fri, 26 Nov 2021 16:03:28 GMT</pubDate>
    <dc:creator>Hubert-Dudek</dc:creator>
    <dc:date>2021-11-26T16:03:28Z</dc:date>
    <item>
      <title>The license of JDBC connector for BI vendors</title>
      <link>https://community.databricks.com/t5/data-engineering/the-license-of-jdbc-connector-for-bi-vendors/m-p/34329#M25098</link>
      <description>&lt;P&gt;Hey all,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We would like to support Databricks in&lt;A href="https://github.com/metriql/metriql" alt="https://github.com/metriql/metriql" target="_blank"&gt; our &lt;/A&gt;BI tool, which is an open-source Java application. (See &lt;A href="https://github.com/metriql/metriql)" target="test_blank"&gt;https://github.com/metriql/metriql)&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In order to connect Databricks, we need to use the JDBC connector similar to the other BI tools such as Looker, and looking at the &lt;A href="https://databricks.com/spark/jdbc-drivers-download" alt="https://databricks.com/spark/jdbc-drivers-download" target="_blank"&gt;JDBC page&lt;/A&gt;, it's not open-source and we need to agree on the &lt;A href="https://databricks.com/jdbc-odbc-driver-license" alt="https://databricks.com/jdbc-odbc-driver-license" target="_blank"&gt;Terms &amp;amp; Conditions&lt;/A&gt; of another company, Magnitude. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The JDBC driver is also not in the Maven repository so we need to download and include it in our repo but I think that it might cause some legal issues. What's the preferred way to integrate Databricks in this case? Is there any other alternative of requiring the user to download the JDBC connector explicitly and somehow include it in the classpath? It wouldn't be an easy path for us as we use Docker image to distribute our application but if that's the only way to make it work, is there any best practice?&lt;/P&gt;</description>
      <pubDate>Fri, 26 Nov 2021 14:53:01 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/the-license-of-jdbc-connector-for-bi-vendors/m-p/34329#M25098</guid>
      <dc:creator>Emre</dc:creator>
      <dc:date>2021-11-26T14:53:01Z</dc:date>
    </item>
    <item>
      <title>Re: The license of JDBC connector for BI vendors</title>
      <link>https://community.databricks.com/t5/data-engineering/the-license-of-jdbc-connector-for-bi-vendors/m-p/34330#M25099</link>
      <description>&lt;P&gt;It doesn't look so bad after all (mean terms and conditions on &lt;A href="https://databricks.com/jdbc-odbc-driver-license" target="test_blank"&gt;https://databricks.com/jdbc-odbc-driver-license&lt;/A&gt; )&lt;/P&gt;&lt;P&gt;but I think the best solution is to open ticket via &lt;A href="https://databricks.com/company/contact" target="test_blank"&gt;https://databricks.com/company/contact&lt;/A&gt;  &lt;/P&gt;</description>
      <pubDate>Fri, 26 Nov 2021 16:03:28 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/the-license-of-jdbc-connector-for-bi-vendors/m-p/34330#M25099</guid>
      <dc:creator>Hubert-Dudek</dc:creator>
      <dc:date>2021-11-26T16:03:28Z</dc:date>
    </item>
  </channel>
</rss>

