Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Not A Bug
-
None
-
None
-
None
-
None
Description
Input setup:
Enable lineage improvements: atlas.lineage.on.demand.enabled=true
Run the following to repro the issue
create database scenario_1; use scenario_1; create table table_1(fname string, lname string, mname string, e_id int, contact_no int); create table table_11 as select * from table_1; create table table_12 as select * from table_1; create table table_13 as select * from table_1; create table table_14 as select * from table_1;
Payload
{ "<scenario_1.table_1.guid>": { "direction": "INPUT", "inputRelationsLimit": 1 } }
Response:
{ "baseEntityGuid": "f92a6057-f6c8-4c0e-a3a0-50dba5f507d3", "lineageDirection": "INPUT", "lineageDepth": 3, "guidEntityMap": {}, "relations": [], "relationsOnDemand": {}, "lineageOnDemandPayload": { "f92a6057-f6c8-4c0e-a3a0-50dba5f507d3": { "direction": "INPUT", "inputRelationsLimit": 1, "outputRelationsLimit": 3, "depth": 3 } } }
Attachments
Issue Links
- is related to
-
ATLAS-4606 Improve Atlas Lineage API performance (fetch on-demand)
- Resolved