[ATLAS-4645] [Lineage Improvements] When inputRelationsLimit or outputRelationsLimit is 0, then it is replaced with the default value of node count

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 3.0.0, 2.3.0
• Assignee: Radhika Kundam
• Reporter: Dharshana M Krishnamoorthy
• Created: 22/Jul/22 17:53
• Updated: 29/Jul/22 17:18
• Resolved: 29/Jul/22 17:15

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 

With the following payload

 {
    "<scenario_1.table_1.guid>": {
        "direction": "BOTH",
        "inputRelationsLimit": 3,
        "outputRelationsLimit": 0
    }
}

The 'lineageOnDemandPayload' should be same as that of the input. Here we can see it is replaces with the default node count value 3.Check "outputRelationsLimit" in the below response

{
    "baseEntityGuid": "f92a6057-f6c8-4c0e-a3a0-50dba5f507d3",
    "lineageDirection": "BOTH",
    "lineageDepth": 3,
    

...

    "lineageOnDemandPayload": {
        "f92a6057-f6c8-4c0e-a3a0-50dba5f507d3": {
            "direction": "BOTH",
            "inputRelationsLimit": 3,
            "outputRelationsLimit": 3,
            "depth": 3
        }
    }
} 

Issue Links

• is duplicated by: ATLAS-4643 [Lineage Improvements] Incorrect response when inputRelationsLimit and outputRelationsLimit is 0
• is fixed by: ATLAS-4606 Improve Atlas Lineage API performance (fetch on-demand)