GET (Specified Table Dependencies) - Teradata Ecosystem Manager

Teradata Ecosystem Manager API Reference

Product
Teradata Ecosystem Manager
Release Number
16.00
Published
December 2016
Language
English (United States)
Last Update
2018-03-29
dita:mapPath
qvc1470238851347.ditamap
dita:ditavalPath
ft:empty
dita:id
B035-3204
lifecycle
previous
Product Category
Analytical Ecosystem

Purpose

Get table dependencies.

URL

/emrest/datadiscovery/databases/{database-name}/tables/{table-name}/dependencies

HTTP Method

GET

Request Parameters

Path variable:database-name, table-name

Response

Response body in JSON with the following parameters.
Name Description Data Type
applications Application details JSON object (Shown in Applications JSON Description table).
jobs Job details JSON object (Shown in Jobs JSON Description table).
workflows Workflow details JSON object (Shown in Workflows JSON Description table).
servers Server details JSON object (Shown in Servers JSON Description table).
Applications JSON parameters are as follows
Applications JSON Description
Name Description Data Type
application_name Name of application String
condition Condition of application String
state State of application String
.
Jobs JSON Description
Name Description Data Type
job_name Name of the job String
job_type Type of job String
server_name Name of the server connected to the job String
status Status of the job String
condition Condition of the job String
Workflows JSON Description
Name Description Data Type
workflow_name Name of the workflow String
execution_status Execution status String
execution_details Execution details JSON Object
Server JSON Description
Name Description Data Type
server_name Name of the server String
server_type Type of server String
data_center Data center String

Status

A status code of 200 is returned on a successful completion. A non-200 status code is returned if an error occurs.

Example: Get Table Dependencies

{
    "jobs": [
        {
            "job_name": "sdjob3",
            "job_type": "MLOAD",
            "status": "SUCCESS",
            "condition": "Normal",
            "server_name": "banjo"
        }
    ],
    "servers": [
        {
            "server_name": "banjo",
            "server_type": "TD",
            "data_center": "UNKNOWN"
        }
    ],
    "applications": [
        {
            "application_name": "app5",
            "condition": "Critical",
            "state": "Active"
        }
    ],
    "workflows": [
        {
            "workflow_name": "sanwf3",
            "execution_status": "SUCCESS",
            "execution_details": {
                "run_id": 127,
                "start_ts": "2016-12-07T18:43:24.480Z",
                "end_ts": "2016-12-07T18:43:36.440Z"
            }
        }
    ]
}