How You Should Save the Output of your Spark ETL Jobs (If you are not Writing to a Database)

Author(s): ___

Originally published on Towards AI.

In this article, I will share my thoughts on the best way to save the output of Spark ETL jobs so that it is easier to do analytical work later. The code to reproduce the examples can be found here.

The cluster I used to run the code in this article is hosted on Databricks with the following configuration:

Cluster Mode: StandardDatabricks Runtime Version: 5.5 LTS ML (includes Apache Spark 2.4.3 Scala 2.11)

There are 8 workers and both the workers and driver are m4.xlarge instances (16.0 GB, 4 Cores).

Imagine you are in the following scenario:

You just joined an immensely popular online retailer… Read the full blog for free on Medium.

Join thousands of data leaders on the AI newsletter. Join over 80,000 subscribers and keep up to date with the latest developments in AI. From research to projects and ideas. If you are building an AI startup, an AI-related product, or a service, we invite you to consider becoming a sponsor.

Published via Towards AI