<?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: Why a new project  instead of putting this in Apache Spark itself in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/why-a-new-project-instead-of-putting-this-in-apache-spark-itself/m-p/19946#M13452</link>
    <description>&lt;P&gt;1. We want a venue in which we can rapidly iterate and make new releases. The overhead of making a release as a separate project is minuscule (in the order of minutes). A release on Spark takes a lot longer (in the order of days)&lt;/P&gt;&lt;P&gt;2. Koalas takes a different approach that might contradict Spark’s API design principles, and those principles cannot be changed lightly given the large user base of Spark. A new, separate project provides an opportunity for us to experiment with new design principles.&lt;/P&gt;</description>
    <pubDate>Fri, 25 Jun 2021 12:42:58 GMT</pubDate>
    <dc:creator>User16826994223</dc:creator>
    <dc:date>2021-06-25T12:42:58Z</dc:date>
    <item>
      <title>Why a new project  instead of putting this in Apache Spark itself</title>
      <link>https://community.databricks.com/t5/data-engineering/why-a-new-project-instead-of-putting-this-in-apache-spark-itself/m-p/19945#M13451</link>
      <description />
      <pubDate>Fri, 25 Jun 2021 12:42:34 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/why-a-new-project-instead-of-putting-this-in-apache-spark-itself/m-p/19945#M13451</guid>
      <dc:creator>User16826994223</dc:creator>
      <dc:date>2021-06-25T12:42:34Z</dc:date>
    </item>
    <item>
      <title>Re: Why a new project  instead of putting this in Apache Spark itself</title>
      <link>https://community.databricks.com/t5/data-engineering/why-a-new-project-instead-of-putting-this-in-apache-spark-itself/m-p/19946#M13452</link>
      <description>&lt;P&gt;1. We want a venue in which we can rapidly iterate and make new releases. The overhead of making a release as a separate project is minuscule (in the order of minutes). A release on Spark takes a lot longer (in the order of days)&lt;/P&gt;&lt;P&gt;2. Koalas takes a different approach that might contradict Spark’s API design principles, and those principles cannot be changed lightly given the large user base of Spark. A new, separate project provides an opportunity for us to experiment with new design principles.&lt;/P&gt;</description>
      <pubDate>Fri, 25 Jun 2021 12:42:58 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/why-a-new-project-instead-of-putting-this-in-apache-spark-itself/m-p/19946#M13452</guid>
      <dc:creator>User16826994223</dc:creator>
      <dc:date>2021-06-25T12:42:58Z</dc:date>
    </item>
  </channel>
</rss>

