Project: SeaTunnel (App Definition and Development / Streaming & Messaging)
File: S3-Redshift.md

The way of S3Redshift is to write data into S3, and then use Redshift's COPY command to import data from S3 to Redshift. Output data to AWS Redshift. Tips: We based on the to implement this connector. So you can use the same configuration as S3File. We made some trade-offs in order to support more file types, so we used the HDFS protocol for internal access to S3 and this connector need some hadoop dependencies. It's only support hadoop version 2.6.5+. By default, we use 2PC commit to ensure `exactly-once` [x] file format type [x] text [x] csv [x] parquet [x] orc [x] json | name | type | required | default value | |-||-|--| | jdbc_url | string | yes | - | | jdbc_user | string | yes | - | | jdbc_password | string | yes | - | | execute_sql | string | yes | - | | path | string | yes | - | | bucket | string | yes | - | | access_key | string | no | - | | access_secret | string | no | - | | hadoops3properties | map | no | - | | filenameexpression | string | no | "${transactionId}" | | fileformattype | string | no | "text" | | filenametimeformat | string | no | "yyyy.MM.dd" | | field_delimiter | string | no | '\001' | | row_delimiter | string | no | "\n" | | partition_by | array | no | - | | partitiondirexpression | string | no | "${k0}=${v0}/${k1}=${v1}/.../${kn}=${vn}/" | | ispartitionfieldwritein_file | boolean | no | false | | sink_columns | array | no | When this parameter is empty, all fields are sink columns | | isenabletransaction | boolean | no | true | | batch_size | int | no | 1000000 | | common-options | | no | - | The JDBC URL to connect to the Redshift database. The JDBC user to connect to the Redshift database. The JDBC password to connect to the Redshift database. The SQL to execute after the data is written to S3. eg: ```sql COPY targettable FROM 's3://yourbucket${path}' IAMROLE 'arn:XXX' REGION 'your region' format as json 'auto'; ``` `target_table` is the table name in Redshift. `${path}` is the path of the file written to S3. please confirm your sql include this variable. and don't need replace it. we will replace it when execute sql. IAM_ROLE is the role that has permission to access S3. format is the format of the file written to S3. please confirm this format is same as the file format you set in the configuration. please refer to for more details. please confirm that the role has permission to access S3. The target dir path is required. The bucket address of s3 file system, for example: `s3n://seatunnel-test`, if you use `s3a` protocol, this parameter should be `s3a://seatunnel-test`. The access key of s3 file system. If this parameter is not set, please confirm that the credential provider chain can be authenticated correctly, you could check this The access secret of s3 file system. If this parameter is not set, please confirm that the credential provider chain can be authenticated correctly, you could check this If you need to add a other option, you could add it here and refer to this ``` hadoops3properties { "fs.s3a.aws.credentials.provider" = "org.apache.hadoop.fs.s3a.SimpleAWSCredentialsProvider" } ``` `filenameexpression` describes the file expression which will be created into the

We can add the variable `${now}` or `${uuid}` in the `filenameexpression`, like `test${uuid}${now}`, `${now}` represents the current time, and its format can be defined by specifying the option `filenametimeformat`. Please note that, If `isenabletransaction` is `true`, we will auto add `${transactionId}_` in the head of the file. We supported as the following file types: `text` `csv` `parquet` `orc` `json` Please note that, The final file name will end with the fileformattype's suffix, the suffix of the text file is `txt`. When the format in the `filenameexpression` parameter is `xxxx-${now}` , `filenametimeformat` can specify the time format of the path, and the default value is `yyyy.MM.dd` . The commonly used time formats are listed as follows: | Symbol | Description | |--|--| | y | Year | | M | Month | | d | Day of month | | H | Hour in day (0-23) | | m | Minute in hour | | s | Second in minute | See for detailed time format syntax. The separator between columns in a row of data. Only needed by `text` and `csv` file format. The separator between rows in a file. Only needed by `text` and `csv` file format. Partition data based on selected fields If the `partition_by` is specified, we will generate the corresponding partition directory based on the partition information, and the final file will be placed in the partition directory. Default `partitiondirexpression` is `${k0}=${v0}/${k1}=${v1}/.../${kn}=${vn}/`. `k0` is the first partition field and `v0` is the value of the first partition field. If `ispartitionfieldwritein_file` is `true`, the partition field and the value of it will be written into data file. For example, if you want to write a Hive Data File, Its value should be `false`. Which columns need be written to file, default value is all the columns get from `Transform` or `Source`. The order of the fields determines the order in which the file is actually written. If `isenabletransaction` is true, we will ensure that data will not be lost or duplicated when it is written to the target directory. Please note that, If `isenabletransaction` is `true`, we will auto add `${transactionId}_` in the head of the file. Only support `true` now. The maximum number of rows in a file. For SeaTunnel Engine, the number of lines in the file is determined by `batchsize` and `checkpoint.interval` jointly decide. If the value of `checkpoint.interval` is large enough, sink writer will write rows in a file until the rows in the file larger than `batchsize`. If `checkpoint.interval` is small, the sink writer will create a new file when a new checkpoint trigger. Sink plugin common parameters, please refer to for details. For text file format ```hocon S3Redshift { jdbc_url = "jdbc:redshift://xxx.amazonaws.com.cn:5439/xxx" jdbc_user = "xxx" jdbc_password = "xxxx" executesql="COPY tablename FROM 's3://test${path}' IAM_ROLE 'arn:aws-cn:iam::xxx' REGION 'cn-north-1' removequotes emptyasnull blanksasnull maxerror 100 delimiter '|' ;" access_key = "xxxxxxxxxxxxxxxxx" secret_key = "xxxxxxxxxxxxxxxxx" bucket = "s3a://seatunnel-test" tmp_path = "/tmp/seatunnel" path="/seatunnel/text" row_delimiter="\n" partitiondirexpression="${k0}=${v0}" ispartitionfieldwritein_file=true filenameexpression="${transactionId}_${now}" fileformattype = "text" filenametimeformat="yyyy.MM.dd" isenabletransaction=true hadoops3properties { "fs.s3a.aws.credentials.provider" = "org.apache.hadoop.fs.s3a.SimpleAWSCredentialsProvider" } } ``` For parquet file format ```hocon S3Redshift { jdbc_url = "jdbc:redshift://xxx.amazonaws.com.cn:5439/xxx" jdbc_user = "xxx" jdbc_password = "xxxx" executesql="COPY tablename FROM 's3://test${path}' IAM_ROLE 'arn:aws-cn:iam::xxx' REGION 'cn-north-1' format as PARQUET;" access_key = "xxxxxxxxxxxxxxxxx" secret_key = "xxxxxxxxxxxxxxxxx" bucket = "s3a://seatunnel-test" tmp_path = "/tmp/seatunnel" path="/seatunnel/parquet" row_delimiter="\n" partitiondirexpression="${k0}=${v0}" ispartitionfieldwritein_file=true filenameexpression="${transactionId}_${now}" fileformattype = "parquet" filenametimeformat="yyyy.MM.dd" isenabletransaction=true hadoops3properties { "fs.s3a.aws.credentials.provider" = "org.apache.hadoop.fs.s3a.SimpleAWSCredentialsProvider" } } ``` For orc file format ```hocon S3Redshift { jdbc_url = "jdbc:redshift://xxx.amazonaws.com.cn:5439/xxx" jdbc_user = "xxx" jdbc_password = "xxxx" executesql="COPY tablename FROM 's3://test${path}' IAM_ROLE 'arn:aws-cn:iam::xxx' REGION 'cn-north-1' format as ORC;" access_key = "xxxxxxxxxxxxxxxxx" secret_key = "xxxxxxxxxxxxxxxxx" bucket = "s3a://seatunnel-test" tmp_path = "/tmp/seatunnel" path="/seatunnel/orc"