How to use JDBC source to write and read data in (Py)Spark?

Question

The goal of this question is to document:

• steps required to read and write data using JDBC connections in PySpark

• possible issues with JDBC sources and know solutions

With small changes these methods should work with other supported languages including Scala and R.

Answer 1

Writing data

1. Include applicable JDBC driver when you submit the application or start shell. You can use for example --packages:

   bin/pyspark --packages group:name:version  
   

   or combining driver-class-path and jars

   bin/pyspark --driver-class-path $PATH_TO_DRIVER_JAR --jars $PATH_TO_DRIVER_JAR
   

   These properties can be also set using PYSPARK_SUBMIT_ARGS environment variable before JVM instance has been started or using conf/spark-defaults.conf to set spark.jars.packages or spark.jars / spark.driver.extraClassPath.

2. Choose desired mode. Spark JDBC writer supports following modes:

   • append: Append contents of this :class:DataFrame to existing data.
   • overwrite: Overwrite existing data.
   • ignore: Silently ignore this operation if data already exists.
   • error (default case): Throw an exception if data already exists.

   Upserts or other fine-grained modifications are not supported

   mode = ...
   

3. Prepare JDBC URI, for example:

   # You can encode credentials in URI or pass
   # separately using properties argument
   # of jdbc method or options
   
   url = "jdbc:postgresql://localhost/foobar"
   

4. (Optional) Create a dictionary of JDBC arguments.

   properties = {
       "user": "foo",
       "password": "bar"
   }
   

   properties / options can be also used to set supported JDBC connection properties.

5. Use DataFrame.write.jdbc

   df.write.jdbc(url=url, table="baz", mode=mode, properties=properties)
   

   to save the data (see pyspark.sql.DataFrameWriter for details).

Known issues:

• Suitable driver cannot be found when driver has been included using --packages (java.sql.SQLException: No suitable driver found for jdbc: ...)

  Assuming there is no driver version mismatch to solve this you can add driver class to the properties. For example:

  properties = {
      ...
      "driver": "org.postgresql.Driver"
  }
  

• using df.write.format("jdbc").options(...).save() may result in:

  java.lang.RuntimeException: org.apache.spark.sql.execution.datasources.jdbc.DefaultSource does not allow create table as select.

  Solution unknown.

• in Pyspark 1.3 you can try calling Java method directly:

  df._jdf.insertIntoJDBC(url, "baz", True)
  

Reading data

1. Follow steps 1-4 from Writing data

2. Use sqlContext.read.jdbc:

   sqlContext.read.jdbc(url=url, table="baz", properties=properties)
   

   or sqlContext.read.format("jdbc"):

   (sqlContext.read.format("jdbc")
       .options(url=url, dbtable="baz", **properties)
       .load())
   

Known issues and gotchas:

• Suitable driver cannot be found - see: Writing data

• Spark SQL supports predicate pushdown with JDBC sources although not all predicates can pushed down. It also doesn't delegate limits nor aggregations. Possible workaround is to replace dbtable / table argument with a valid subquery. See for example:

  • Does spark predicate pushdown work with JDBC?
  • More than one hour to execute pyspark.sql.DataFrame.take(4)
  • How to use SQL query to define table in dbtable?

• By default JDBC data sources loads data sequentially using a single executor thread. To ensure distributed data loading you can:

  • Provide partitioning column (must be IntegeType), lowerBound, upperBound, numPartitions.
  • Provide a list of mutually exclusive predicates predicates, one for each desired partition.

  See:

  • Partitioning in spark while reading from RDBMS via JDBC,
  • How to optimize partitioning when migrating data from JDBC source?,
  • How to improve performance for slow Spark jobs using DataFrame and JDBC connection?
  • How to partition Spark RDD when importing Postgres using JDBC?

• In a distributed mode (with partitioning column or predicates) each executor operates in its own transaction. If the source database is modified at the same time there is no guarantee that the final view will be consistent.

Where to find suitable drivers:

• Maven Repository (to obtain required coordinates for --packages select desired version and copy data from a Gradle tab in a form compile-group:name:version substituting respective fields) or Maven Central Repository:

  • PostgreSQL
  • MySQL

Other options

Depending on the database specialized source might exist, and be preferred in some cases:

• Greenplum - Pivotal Greenplum-Spark Connector
• Apache Phoenix - Apache Spark Plugin
• Microsoft SQL Server - Spark connector for Azure SQL Databases and SQL Server
• Amazon Redshift - Databricks Redshift connector (current versions available only in a proprietary Databricks Runtime. Discontinued open source version, available on GitHub).