Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
0.8.3, 2.1.0
-
None
Description
Two Dataset type entities created and a Process type entity with inputs and outputs attribute as dataset entities respectively is created .
Creating base Entities
To begin with, on a blank installation of Atlas, first two DataSet entities are created through the use of the Atlas REST API. Both entities are created with separate CURL requests to the following REST
endpoint:
POST /api/atlas/v2/entity
Payload for entity 1
{
"entity": {
"typeName": "DataSet",
"attributes": {
"qualifiedName": "dataset1@cluster01",
"name": "DataSet1",
"description": "This is an Example DataSet Created Through the REST API for Lineage",
"owner": "admin"
},
"guid": -1
}
}
Payload for entity 2
{
"entity": {
"typeName": "DataSet",
"attributes": {
"qualifiedName": "dataset2@cluster01",
"name": "DataSet2",
"description": "This is an Example DataSet Created Through the REST API for Lineage",
"owner": "admin"
},
"guid": -1
}
}
Creating a Process Entity
Next a Process entity is created with the following REST API call (Note, the guids for each of the DataSet's were found using the Atlas UI):
POST /api/atlas/v2/entity
Payload
{
"entity": {
"typeName": "Process",
"attributes": {
"qualifiedName": "exampleProcess@cluster01",
"name": "Example Process",
"description": "This is an Example Process Created Through the REST API",
"owner": "admin",
"inputs": [
{
"guid": "3b5c3fce-fb83-4b2b-b95f-0cf76ae88eb6",
"typeName": "DataSet",
"uniqueAttributes": {
"qualifiedName": "dataset1@cluster01"
}
}
],
"outputs": [
{
"guid": "1d019580-86a2-4da3-9146-8bd81c74608b",
"typeName": "DataSet",
"uniqueAttributes": {
"qualifiedName": "dataset2@cluster01"
}
}
]
},
"guid": -1
}
}
The REST API call successfully creates a Process entity within Atlas, which can be found in the UI
In Atlas server lineage entity is created but on Atlas UI the lineage tab is not shown for these entities.