JDBC URL to connect to. The source-specific connection properties may be specified in the URL. For example: - jdbc:postgresql://test.us-east-1.rds.amazonaws.com:5432/postgres - jdbc:mysql://database-mysql.test.us-east-1.rds.amazonaws.com:3306/mysql
Temporary Directory
Location
S3 location to temporarily store data before it’s loaded into Redshift.
Data Source
Location
Strategy to read data. In the Source gem, you can select DB Table or SQL Query. In the Target gem, you must enter a table. To learn more, see DB Table and SQL Query.
Schema
Properties
Schema to apply on the loaded data. In the Source gem, you can define or edit the schema visually or in JSON code. In the Target gem, you can view the schema visually or as JSON code.
The DB Table option dictates which table to use as the source to read from. You can use anything valid in a FROM clause of a SQL query. For example, instead of a table name, use a subquery in parentheses.
The DB Table option and the query parameter are mutually exclusive, which means that you
cannot specify both at the same time.
The SQL Query option specifies which query to use as a subquery in the FROM clause. Spark also assigns an alias to the subquery clause. For example, Spark issues the following query to the JDBC Source:
SELECT columns FROM (<user_specified_query>) spark_gen_alias
The following restrictions exist when you use this option:
You cannot use the query and partitionColumn options at the same time.
If you must specify the partitionColumn option, you can specify the subquery using the dbtable option and qualify your partition columns using the subquery alias provided as part of dbtable.
