You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@atlas.apache.org by "Dharshana M Krishnamoorthy (Jira)" <ji...@apache.org> on 2022/07/22 17:54:00 UTC
[jira] [Created] (ATLAS-4645) [Lineage Improvements] When inputRelationsLimit or outputRelationsLimit is 0, then it is replaced with the default value of node count
Dharshana M Krishnamoorthy created ATLAS-4645:
-------------------------------------------------
Summary: [Lineage Improvements] When inputRelationsLimit or outputRelationsLimit is 0, then it is replaced with the default value of node count
Key: ATLAS-4645
URL: https://issues.apache.org/jira/browse/ATLAS-4645
Project: Atlas
Issue Type: Bug
Reporter: Dharshana M Krishnamoorthy
Input setup:
Enable lineage improvements: *atlas.lineage.on.demand.enabled=true*
Run the following to repro the issue
{code:java}
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; {code}
Payload
With the following payload
{code:java}
{
"<scenario_1.table_1.guid>": {
"direction": "BOTH",
"inputRelationsLimit": 3,
"outputRelationsLimit": 0
}
}{code}
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
{code:java}
{
"baseEntityGuid": "f92a6057-f6c8-4c0e-a3a0-50dba5f507d3",
"lineageDirection": "BOTH",
"lineageDepth": 3,
{code}
{color:#009100}...{color}
{code:java}
"lineageOnDemandPayload": {
"f92a6057-f6c8-4c0e-a3a0-50dba5f507d3": {
"direction": "BOTH",
"inputRelationsLimit": 3,
"outputRelationsLimit": 3,
"depth": 3
}
}
} {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)