<?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 Why is the current limit for rows returned in Databricks SQL 64K? in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/why-is-the-current-limit-for-rows-returned-in-databricks-sql-64k/m-p/21465#M14636</link>
    <description />
    <pubDate>Wed, 23 Jun 2021 14:11:30 GMT</pubDate>
    <dc:creator>User16826992945</dc:creator>
    <dc:date>2021-06-23T14:11:30Z</dc:date>
    <item>
      <title>Why is the current limit for rows returned in Databricks SQL 64K?</title>
      <link>https://community.databricks.com/t5/data-engineering/why-is-the-current-limit-for-rows-returned-in-databricks-sql-64k/m-p/21465#M14636</link>
      <description />
      <pubDate>Wed, 23 Jun 2021 14:11:30 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/why-is-the-current-limit-for-rows-returned-in-databricks-sql-64k/m-p/21465#M14636</guid>
      <dc:creator>User16826992945</dc:creator>
      <dc:date>2021-06-23T14:11:30Z</dc:date>
    </item>
    <item>
      <title>Re: Why is the current limit for rows returned in Databricks SQL 64K?</title>
      <link>https://community.databricks.com/t5/data-engineering/why-is-the-current-limit-for-rows-returned-in-databricks-sql-64k/m-p/21466#M14637</link>
      <description>&lt;P&gt;I believe it's due to limitation in Redash's legacy architecture (which was acquired by Databricks). Hence Databricks is doing great efforts in increasing this threshold (was originally 20K), so with patience it will get to close to 1 Million. In the meantime, it's recommended to run aggregation/reduction operations on your data.&lt;/P&gt;</description>
      <pubDate>Fri, 25 Jun 2021 22:32:32 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/why-is-the-current-limit-for-rows-returned-in-databricks-sql-64k/m-p/21466#M14637</guid>
      <dc:creator>Mooune_DBU</dc:creator>
      <dc:date>2021-06-25T22:32:32Z</dc:date>
    </item>
    <item>
      <title>Re: Why is the current limit for rows returned in Databricks SQL 64K?</title>
      <link>https://community.databricks.com/t5/data-engineering/why-is-the-current-limit-for-rows-returned-in-databricks-sql-64k/m-p/21467#M14638</link>
      <description>&lt;P&gt;@Amine El Helou​&amp;nbsp; when this limit will be lifted? my users won't switch from SSMS to dbx sql unless they can see all results set in UI ( which sometimes is more than 10mm rows) &lt;/P&gt;</description>
      <pubDate>Wed, 11 May 2022 20:42:13 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/why-is-the-current-limit-for-rows-returned-in-databricks-sql-64k/m-p/21467#M14638</guid>
      <dc:creator>prasadvaze</dc:creator>
      <dc:date>2022-05-11T20:42:13Z</dc:date>
    </item>
  </channel>
</rss>

