https://community.databricks.com/t5/data-engineering/spark-reparation-vs-coalesce/m-p/24670#M17175 Mon, 14 Jun 2021 23:06:38 GMT Srikanth_Gupta_ 2021-06-14T23:06:38Z https://community.databricks.com/t5/data-engineering/spark-reparation-vs-coalesce/m-p/24670#M17175 Mon, 14 Jun 2021 23:06:38 GMT https://community.databricks.com/t5/data-engineering/spark-reparation-vs-coalesce/m-p/24670#M17175 Srikanth_Gupta_ 2021-06-14T23:06:38Z https://community.databricks.com/t5/data-engineering/spark-reparation-vs-coalesce/m-p/24671#M17176 <UL><LI><B>coalesce</B> avoids a full shuffle and could be used to decrease the number of partitions</LI><LI><B>repartition</B> results in a full shuffle and could be used to increase or decrease the number of partitions</LI></UL> Thu, 17 Jun 2021 16:43:16 GMT https://community.databricks.com/t5/data-engineering/spark-reparation-vs-coalesce/m-p/24671#M17176 sajith_appukutt 2021-06-17T16:43:16Z