This article is a quick start document for Streamis 0.3.0, which covers the basic usage process of Stremis. More details on operation and usage will be provided in the user documentation.
For the convenience of users,the Streamis system is embedded in the DSS system in the form of DSS components
The entry path is Home-DSS component application-Enter Streamis
Picture 2.1 Streamis entrance]Entering the homepage, the top half shows the core indicators.
The core indicator shows the status summary of the Flink tasks uploaded to the project for execution. There are temporarily 7 states, showing the state name and the number of tasks in that state. The specific content is as shown in the figure below.
Picture 3.1 Core indicators Support the release of Flink Jar and Flink SQL, and provide the development and debugging and production management capabilities of streaming applications, such as: start and stop, status monitoring, checkpoint, etc.
Click "Upload" and select the zip file to upload. The file is divided into two job types, Flink Jar and Flink SQL, and the format is as follows:
Picture 4.1 Flink Jar ZIP{
"projectName": "flinkJarTest3",
"jobName": "flinkJarTestc",
"jobType": "flink.jar",
"tags": "e,t,y,h,g",
"description": "test of FlinkJar Job3",
"jobContent": {
"main.class.jar": "frauddetection-0.1.jar",
"main.class": "spendreport.FraudDetectionJob",
"args": ["aa","bb"],
"hdfs.jars": [],
"dependency.jars": [],
"resources": []
}
}
The SQL type file is just a ZIP compressed package of the meta.json file, and its content is as follows:
{
"projectName": "flinkSqlTestD",
"jobName": "flinkSqlTesta",
"jobType": "flink.sql",
"tags": "a,b,c",
"description": "test FlinkSql JobD",
"jobContent": {
"type": "sql",
"sql": "select 1",
"file": "",
"resourceId": "",
"version": ""
}
}
After the ZIP file is uploaded successfully, the task is displayed in the task list in Figure 3.1, and operations such as start, stop, configuration and checkpoint are provided according to the task status;
The task list provides the function of "query", where job name provides the function of fuzzy query.
Click "job name" of a task in the task list to provide the function of managing the task, or click "three dots" to the left of the name to call up the specific function configuration entry, as shown below:
Picture4.3 Configuration jobThe configuration task provides four functions, namely:
- Parameter configuration
- alarm configuration
- operation history
- operation log
- snapshot[savepoint]
Click batch operation, and multiple job tasks can be restarted. Restart and snapshot will generate a snapshot and then restart. Restart directly will not generate a snapshot.
Picture 4.4 Job summaryThe running status summarizes the real-time traffic, total amount of data, and load status of the task.
Picture 4.5 Job history
The running history records the record of each run of the task.
Picture 4.6 Job config
The configuration page is used to configure various parameters of the running task, and provides the following types of configuration:
- Resource configuration
- Production configuration
- Flink parameters
- Permission settings
The job details are divided into two display interfaces according to the task type Flink Jar and Flink SQL.
Flink Jar Job details
Picture 4.7 Flink Jar Job detailsFlink Jar task details show the contents and parameters of the task Jar package, and provide the function of downloading the Jar package.
Flink SQL job details
Picture 4.8 Flink SQL job detailsThe Flink SQL job details show the SQL statement of the task.
Page entry: On the top right of the homepage-core indicators "Project Resource File".
The project resource file provides the function of uploading and managing the resource files required by the project, as shown in the figure below:
Picture 5.1 Engineering Documents Home Page
Picture 5.2 Upload project file