-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/71902/
-----------------------------------------------------------
(Updated Dec. 12, 2019, 3:20 p.m.)
Review request for atlas, Ashutosh Mestry, Aadarsh Jajodia, keval bhatt,
Sridhar K, Le Ma, Mandar Ambawane, mayank jain, Nixon Rodrigues, Sameer Shaikh,
and Sarath Subramanian.
Changes
-------
addressed review comments.
Bugs: ATLAS-3558
https://issues.apache.org/jira/browse/ATLAS-3558
Repository: atlas
Description
-------
Lineage in atlas uses graph query to compute lineage across entities (inputs,
outputs or both). Lineage rendering performance have degraded after using
janusgraph version 0.4.0
On investigation, lineage graph query initialization and execution using
gremlin script engine has been found to be the bottleneck.
Alternate in-memory computation of lineage has improved performance by many
folds (~90% improvement). This Jira is about adding alternate in-memory
computation of lineage.
"atlas.use.graph.query.for.lineage" property can be used to toggle between
graph query and in-memory computation of lineage. The default option will be
in-memory.
Diffs (updated)
-----
intg/src/main/java/org/apache/atlas/AtlasConfiguration.java 979bd0ae3
repository/src/main/java/org/apache/atlas/discovery/EntityLineageService.java
9a020468d
Diff: https://reviews.apache.org/r/71902/diff/2/
Changes: https://reviews.apache.org/r/71902/diff/1-2/
Testing
-------
Precommit:
https://builds.apache.org/view/A/view/Atlas/job/PreCommit-ATLAS-Build-Test/1581/console
Manually validated lineage rendering works fine for simple, complex and
circular lineages.
Thanks,
Sarath Subramanian
