GOVERNATLAS / PRODUCT DOSSIER

Cloudera Data Lineage

Cloudera identifies Data Lineage as formerly Octopai and describes lineage across databases, ETL jobs and BI outputs. Legacy contracts and feature continuity are not established.

Explore the product ↗Add to comparison ↗

01 / CONTEXT & SCOPE

Understand the proposition.
Define the boundary.

The decision to make

Evaluate a dependency question that crosses the systems you actually operate. The important result is a reconstructable path with visible gaps, not simply a large graph. Keep the current product identity distinct from assumptions about historical Octopai contracts and support arrangements.

What this record does not establish

Cloudera explicitly identifies the product as formerly Octopai. This supports identity continuity, not legacy contract rights, exhaustive extraction coverage or accuracy of every inferred relationship.

1 current source · 1 published assertion
Source coverage is a research boundary, not a quality score.

02 / YOUR EVALUATION

Turn interest into a useful trial.

Open the evaluation playbook ↗

A test worth running

Trace a synthetic field through a source, transformation and BI output. Include one custom or unsupported step and inspect how the gap is represented. Change the transformation and ask an engineer to identify the affected outputs using the preserved before-and-after context.

GovernAtlas editorial proposal. We have not performed this test.

Evidence to bring back

Distinguish automatically extracted, inferred and manually supplied links in the pilot result.
Report coverage against a known source manifest, including the unsupported path and its operating owner.

03 / DOCUMENTED EVIDENCE

Read the claim. Inspect the basis.

Each statement retains its classification and preserved source. A vendor assertion is not an independent test result.

vendor asserted

Cloudera identifies Data Lineage as formerly Octopai and describes lineage across databases, ETL jobs and BI outputs. Legacy contracts and feature continuity are not established. Scope: vendor documentation; no independent testing or blanket entitlement is established.

Source, dates & preserved provenance

Cloudera Data Lineage — official product overview ↗

Authority: vendor owned
Observed 2026-10-15 · Reviewed 2026-10-15 · current until 2026-11-14

Artifact SHA-256: 7bc5e0418eef973d7ad7c5380510bde689c0ed8be41c3041ed1196da78e72951

The hash identifies the preserved capture. The live source may have changed.

Source register

Cloudera Data Lineage — official product overview ↗vendor owned · captured 2026-10-15

Brand asset provenance

Organization identity asset from its official website; inclusion does not imply endorsement.

Official website ↗ · Original asset ↗

04 / BEFORE YOU COMMIT

Better questions.
A clearer decision.

Resolve these with the provider and your own evaluation team.

Which source technologies and transformations are captured, and how are unsupported or manually represented dependencies identified?

Can the vendor demonstrate a change to a data asset and export the affected ownership and decision history?

Which evidence is available for permissions, retention and failure handling in the quoted environment?

Regulatory applicability requires a separate, current determination. Inclusion is not certification.

KEEP THE RECORD USEFUL

A dossier should stand up to scrutiny.

Have a source that changes this picture? Submit it for editorial review.

Raise an evidence issue ↗