Realtime Compute for Apache Flink:Develop a Python API draft

References

You can develop Flink business code in your on-premises environment. After the business code is developed, you must upload the business code to the development console of Realtime Compute for Apache Flink and publish the business code as a deployment.

• For more information about how to develop business code of Apache Flink 1.17, see Python API.

• Issues may occur when you develop code in Apache Flink. For more information about the issues and fixes, see FAQ.

Debug a deployment

@udf(result_type=DataTypes.BIGINT())
def add(i, j):    
  logging.info("hello world")    
  return i + j

Use a connector

For more information about the connectors supported by Realtime Compute for Apache Flink, see Supported connectors. To use a connector, perform the following steps:

1. Log on to the Realtime Compute for Apache Flink console.

2. Find the workspace that you want to manage and click Console in the Actions column.

3. In the left-side navigation pane, click Artifacts.

4. On the Artifacts page, click Upload Artifact and select the Python package of the desired connector that you want to upload.

   You can upload the Python package of a connector that you develop or a connector provided by Realtime Compute for Apache Flink. You can visit Connectors to download the official Python packages provided by Realtime Compute for Apache Flink.

5. On the Deployments page, click Create Deployment. In the Create Deployment dialog box, select the Python package of the desired connector from the drop-down list of Additional Dependencies and configure other parameters to create a deployment.

6. On the Deployments page, click the name of the created deployment. In the upper-right corner of the Parameters section on the Configuration tab, click Edit. Then, enter the location information of the Python package of the desired connector in the Other Configuration field.

   If your deployment depends on the Python packages of multiple connectors and the packages are named connector-1.jar and connector-2.jar, configure the following information:

   pipeline.classpaths: 'file:///flink/usrlib/connector-1.jar;file:///flink/usrlib/connector-2.jar'