Print

Function

The Print connector is used to print output data to the error file or out file in the TaskManager, making it easier for you to view the result in code debugging.

Prerequisites

None

Caveats

• The Print result table supports the following output formats:

  Print	Condition 1	Condition 2
  Identifier:Task ID> Output data	A print identifier prefix must be provided. That is, you must specify print-identifier in the WITH parameter when creating the Print result table.	parallelism > 1
  Identifier> Output data	A print identifier prefix must be provided. That is, you must specify print-identifier in the WITH parameter when creating the Print result table.	parallelism == 1
  Task ID> Output data	A print identifier prefix is not needed. That is, you do not specify print-identifier in the WITH parameter when creating the Print result table.	parallelism > 1
  Output data	A print identifier prefix is not needed. That is, you do not specify print-identifier in the WITH parameter when creating the Print result table.	parallelism == 1

• When you create a Flink OpenSource SQL job, set Flink Version to 1.15 in the Running Parameters tab. Select Save Job Log, and specify the OBS bucket for saving job logs.

Syntax

1
2
3
4
5
6
7
8
9

create table printSink (
  attr_name attr_type 
  (',' attr_name attr_type) * 
  (',' PRIMARY KEY (attr_name,...) NOT ENFORCED)
) with (
  'connector' = 'print',
  'print-identifier' = '',
  'standard-error' = ''
);

Parameter Description

Example

Create a Flink OpenSource SQL job. Run the following script to generate random data through the DataGen table and output the data to the Print result table.

create table dataGenSource(
  user_id string,
  amount int
) with (
  'connector' = 'datagen',
  'rows-per-second' = '1', --Generates a piece of data per second.
  'fields.user_id.kind' = 'random', --Specifies a random generator for the user_id field.
  'fields.user_id.length' = '3' --Limits the length of user_id to 3.
);

create table printSink(
  user_id string,
  amount int
) with (
  'connector' = 'print',
  'print-identifier' = '', --Configure the data prefix.
  'standard-error' = 'false', --Output data to the out file of TaskManager.
  'sink.parallelism' = '2' --Configure the parallelism.
);

insert into printSink select * from dataGenSource;

After the job is submitted, the job status changes to Running. You can perform the following operations of either method to view the output result:

• Method 1:
  1. Log in to the DLI console. In the navigation pane, choose Job Management > Flink Jobs.
  2. Locate the row that contains the target Flink job, and choose More > FlinkUI in the Operation column.
  3. On the Flink UI, choose Task Managers, click the task name, and select Stdout to view job logs.
• Method 2: If you select Save Job Log on the Running Parameters tab before submitting the job, perform the following operations:
  1. Log in to the DLI console. In the navigation pane, choose Job Management > Flink Jobs.
  2. Click the name of the corresponding Flink job, choose Run Log, click OBS Bucket, and locate the folder of the log you want to view according to the date.
  3. Go to the folder of the date, find the folder whose name contains taskmanager, download the taskmanager.out file, and view result logs.
• Method 3: If the queue is a new version, perform the following operations:
  1. Log in to the DLI console. In the navigation pane, choose Job Management > Flink Jobs.
  2. In the job list, click the name of your desired Flink job. On the displayed page, click the Logs tab.
  3. Select the corresponding TaskManager name from the drop-down list in the upper left corner and click the taskmanager.out file to view its result log.