File System Sink Stream (Recommended)

Function

You can create a sink stream to export data to a file system such as HDFS or OBS. After the data is generated, a table can be created directly according to the generated directory. The table can be processed through DLI SQL, and the output data directory can be stored in partitioned tables. It is applicable to scenarios such as data dumping, big data analysis, data backup, and active, deep, or cold archiving.

OBS is an object-based storage service. It provides massive, secure, highly reliable, and low-cost data storage capabilities.

Syntax

1
2
3
4
5
6
7
8
9

CREATE SINK STREAM stream_id (attr_name attr_type (',' attr_name attr_type)* )
  [PARTITIONED BY (attr_name (',' attr_name)*]
  WITH (
    type = "filesystem",
    file.path = "obs://bucket/xx",
    encode = "parquet",
    ak = "",
    sk = ""
  );

Keywords

Precautions

• To ensure job consistency, enable checkpointing if the Flink job uses the file system output stream.
• To avoid data loss or data coverage, you need to enable automatic or manual restart upon job exceptions. Enable the Restore Job from Checkpoint.
• Set the checkpoint interval after weighing between real-time output file, file size, and recovery time, such as 10 minutes.
• Two modes are supported.
  • At least once: Events are processed at least once.
  • Exactly once: Events are processed only once.
• When you use sink streams of a file system to write data into OBS, do not use multiple jobs for the same directory.
  • The default behavior of an OBS bucket is overwriting, which may cause data loss.
  • The default behavior of the OBS parallel file system bucket is appending, which may cause data confusion.

  You should carefully select the OBS bucket because of the preceding behavior differences. Data exceptions may occur after abnormal job restart.

HDFS Proxy User Configuration

1. Log in to the MRS management page.
2. Select the HDFS NameNode configuration of MRS and add configuration parameters in the Customization area.

   In the preceding information, myname in the core-site values hadoop.proxyuser.myname.hosts and hadoop.proxyuser.myname.groups is the name of the krb authentication user.

   

   Ensure that the permission on the HDFS data write path is 777.

3. After the configuration is complete, click Save.

Example

• Example 1:

  The following example dumps the car_info data to OBS, with the buyday field as the partition field and parquet as the encoding format.

  1 2 3 4 5 6 7 8 9 10 11 12 13

  create sink stream car_infos ( carId string, carOwner string, average_speed double, buyday string ) partitioned by (buyday) with ( type = "filesystem", file.path = "obs://obs-sink/car_infos", encode = "parquet", ak = "{{myAk}}", sk = "{{mySk}}" );

  The data is ultimately stored in OBS. Directory: obs://obs-sink/car_infos/buyday=xx/part-x-x.

  After the data is generated, the OBS partitioned table can be established for subsequent batch processing through the following SQL statements:

  1. Create an OBS partitioned table.

     1 2 3 4 5 6 7 8

     create table car_infos ( carId string, carOwner string, average_speed double ) partitioned by (buyday string) stored as parquet location 'obs://obs-sink/car_infos';

  2. Restore partition information from the associated OBS path.

     1	alter table car_infos recover partitions;

• Example 2:

  The following example dumps the car_info data to HDFS, with the buyday field as the partition field and csv as the encoding format.

  1 2 3 4 5 6 7 8 9 10 11 12

  create sink stream car_infos ( carId string, carOwner string, average_speed double, buyday string ) partitioned by (buyday) with ( type = "filesystem", file.path = "hdfs://node-master1sYAx:9820/user/car_infos", encode = "csv", field_delimiter = "," );

  The data is ultimately stored in HDFS. Directory: /user/car_infos/buyday=xx/part-x-x.