[ATLAS-3558] Improve lineage performance using in-memory traversal

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0.0
• Fix Version/s: 2.1.0
• Component/s: atlas-core
• Assignee: Sarath Subramanian
• Reporter: Sarath Subramanian
• Created: 11/Dec/19 23:42
• Updated: 14/Dec/19 05:50
• Resolved: 14/Dec/19 05:49

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.lineage.query.use.gremlin" property can be used to toggle between graph query and in-memory computation of lineage. The default option will be in-memory.

Issue Links

• links to: Code review
• links to: Precommit