Bu sayfa henüz yerel dilinizde mevcut değildir. Daha fazla dil seçeneği eklemek için yoğun bir şekilde çalışıyoruz. Desteğiniz için teşekkür ederiz.
- What's New
- Service Overview
-
User Guide
- Preparations
- IAM Permissions Management
- Data Management
- Data Integration
- Data Development
- Solution
- O&M and Scheduling
- Configuration and Management
- Specifications
- Usage Tutorials
-
References
-
Nodes
- Node Overview
- CDM Job
- DIS Stream
- DIS Dump
- DIS Client
- Rest Client
- Import GES
- MRS Kafka
- Kafka Client
- CS Job
- DLI SQL
- DLI Spark
- DWS SQL
- MRS SparkSQL
- MRS Hive SQL
- MRS Presto SQL
- MRS Spark
- MRS Spark Python
- MRS Flink Job
- MRS MapReduce
- CSS
- Shell
- RDS SQL
- ETL Job
- OCR
- Create OBS
- Delete OBS
- OBS Manager
- Open/Close Resource
- Data Quality Monitor
- Subjob
- SMN
- Dummy
- For Each
- EL
-
Nodes
- Change History
- API Reference
-
FAQs
- What Is DLF?
- What Is DLF Used For?
- What Is a Job?
- How Many Jobs Can Be Created in DLF?
- Can I Adjust the Job Quota in DLF?
- Does DLF Provide Job Templates?
- What Is a Node?
- Is There a Limit on the Number of Nodes Contained in a DLF Job?
- How Can I Quickly Rectify a Deleted CDM Cluster Associated with a Job?
- What Causes a Large Difference Between the Plan Time and Start Time of a Job?
- How Do I Change the Message Language?
- What Can I Do When a Job Fails?
- Glossary
- General Reference
Show all
Copied.
Job Embedded Objects
A job object provides properties and methods of obtaining the output message, job scheduling plan time, and job execution time of the previous node in a job.
Properties and Methods
Property |
Type |
Description |
---|---|---|
name |
String |
Name of the job. |
planTime |
java.util.Date |
Job scheduling plane time, that is, the time configured for periodic scheduling, for example, to schedule a job at 1:01 a.m. every day. |
startTime |
java.util.Date |
Job execution time. It may be the same as or later than the planTime (because the job engine is busy). |
eventData |
String |
Message obtained from the DIS stream when the event-driven scheduling is used. |
projectId |
String |
ID of the project where DLF is located. |
Method |
Description |
---|---|
String getNodeStatus(String nodeName) |
Obtains the running status of a specified node. If the node runs properly, success is returned. If the node fails to run, fail is returned. For example, the following condition can be used to determine whether a node is successfully executed: #{(Job.getNodeStatus("test")) == "success" } |
String getNodeOutput(String nodeName) |
Obtains the output of a specified node. This method can only obtain the output of the previous dependent node. Currently, only the output of the Rest Client node, that is, the returned message of the REST request, can be obtained. |
String getParam(String key) |
Obtains a job parameter. |
String getPlanTime(String pattern) |
Obtains the plan time character string in a specified pattern. Pattern indicates the date and time mode. For details, see Date and Time Mode. |
String getYesterday(String pattern) |
Obtains the time character string of the day before the plan time. Pattern indicates the date and time mode. For details, see Date and Time Mode. |
String getLastHour(String pattern) |
Obtains the time character string of last hour before the plan time. Pattern indicates the date and time mode. For details, see Date and Time Mode. |
String getRunningData(String nodeName) |
Obtains the data recorded during the running of a specified node. This method can only obtain the output of the previous dependent node. Currently, only the DLI job ID recorded during the running of the DLI SQL node can be obtained. For example, to obtain the job ID in the third statement of DLI node DLI_INSERT_DATA, run the following command: #{JSONUtil.path(Job.getRunningData("DLI_INSERT_DATA"),"jobIds[2]")} |
String getInsertJobId(String nodeName) |
Returns the job ID in the first DLI Insert SQL statement of the specified DLI SQL or Transform Load node. If the nodeName parameter is not specified, the job ID in the first DLI Insert SQL statement of the DLI SQL node is obtained. If the job ID cannot be obtained, the null value is returned. |
Example
The expression used to obtain the output of node test in the job is as follows:
#{Job.getNodeOutput("test")}
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot