<?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: Snowflake connector in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/snowflake-connector/m-p/57470#M30796</link>
    <description>&lt;P&gt;Thanks !!&lt;/P&gt;</description>
    <pubDate>Tue, 16 Jan 2024 14:46:23 GMT</pubDate>
    <dc:creator>Phani1</dc:creator>
    <dc:date>2024-01-16T14:46:23Z</dc:date>
    <item>
      <title>Snowflake connector</title>
      <link>https://community.databricks.com/t5/data-engineering/snowflake-connector/m-p/57400#M30770</link>
      <description>&lt;P&gt;Hi Team, Databricks recommends storing data in a cloud storage location, but if we directly connect to Snowflake using the Snowflake connector, will we face any performance issues?&lt;/P&gt;&lt;P&gt;Could you please suggest the best way to read a large volume of data from Snowflake to Databricks?&lt;/P&gt;</description>
      <pubDate>Tue, 16 Jan 2024 05:13:46 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/snowflake-connector/m-p/57400#M30770</guid>
      <dc:creator>Phani1</dc:creator>
      <dc:date>2024-01-16T05:13:46Z</dc:date>
    </item>
    <item>
      <title>Re: Snowflake connector</title>
      <link>https://community.databricks.com/t5/data-engineering/snowflake-connector/m-p/57420#M30774</link>
      <description>&lt;P&gt;If you read data from Snowflake in Spark using e.g.&amp;nbsp;&lt;SPAN&gt;spark.read.jdbc it will be slow.&amp;nbsp;&lt;/SPAN&gt;This is because the data is loaded in a single step, and is therefore loaded by a single executor.&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;You need to somehow distributing the query among the spark executors, and assign each executor to read a subset of the result, eg. by adding WHERE conditions or limit-offset clauses, and distribute them among the executors.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;JDBC method has also option to supply following information&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;partitionColumn,&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;lowerBound,&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;upperBound, and&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;numPartitions&lt;SPAN&gt;&amp;nbsp;, then you can paralelize it.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Another way is to sync data into DeltaLake and run your query against delta table.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;-------&lt;BR /&gt;UPDATE: there is also one more way but would require redesign on Snoflake end -&amp;gt; to create table in Snowflake as External Iceberg table and connect your Databricks job to Iceberg but that might be overkill.&lt;/P&gt;</description>
      <pubDate>Tue, 16 Jan 2024 09:31:54 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/snowflake-connector/m-p/57420#M30774</guid>
      <dc:creator>Wojciech_BUK</dc:creator>
      <dc:date>2024-01-16T09:31:54Z</dc:date>
    </item>
    <item>
      <title>Re: Snowflake connector</title>
      <link>https://community.databricks.com/t5/data-engineering/snowflake-connector/m-p/57470#M30796</link>
      <description>&lt;P&gt;Thanks !!&lt;/P&gt;</description>
      <pubDate>Tue, 16 Jan 2024 14:46:23 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/snowflake-connector/m-p/57470#M30796</guid>
      <dc:creator>Phani1</dc:creator>
      <dc:date>2024-01-16T14:46:23Z</dc:date>
    </item>
  </channel>
</rss>

