Skip to main content

What does Atlan crawl from Cube?

Connect docs via MCP

Atlan extracts your Cube semantic model and maps each Cube concept to a dedicated Atlan asset type. The tables below list which Cube properties are read and how they appear on the corresponding Atlan asset. A 🔀 next to a section heading marks an asset type that participates in lineage. Atlan supports the following lineage:

  • Upstream warehouse lineage: from the warehouse Table and Column assets each cube and member is built on, into the cube and member, rendered as Process entities (Table → Process → CubeCube, Column → Process → member). These resolve against the upstream warehouse connection you have already cataloged in Atlan.
  • Intra-model lineage: from a cube into the views built on it (CubeCube → Process → CubeView), and from a cube member into the view member that projects it (member → Process → member).

Data sources

Atlan maps each Cube deployment-and-environment to a CubeDataSource asset—the root container for everything crawled in that run.

Source propertyAtlan propertyWhere in Atlan
Environment namenameasset profile and overview sidebar
Deployment iddeploymentIdasset profile
Environment idenvironmentIdasset profile
Environment type (for example, production)environmentTypeasset profile
Environment branchenvironmentBranchasset profile
Count of cubes in the modelcubeCubeCountasset profile
Count of views in the modelcubeViewCountasset profile

Cubes 🔀

Atlan maps cubes from Cube to its CubeCube asset type. A cube is the foundational entity in the semantic model, built directly on warehouse tables.

Source propertyAtlan propertyWhere in Atlan
Cube namenameasset profile and overview sidebar
Cube descriptiondescriptionasset profile and overview sidebar
Parent data sourcecubeDataSource (relationship)asset profile—links back to the CubeDataSource
Count of dimensionscubeDimensionCountasset profile
Count of measurescubeMeasureCountasset profile
Count of segmentscubeSegmentCountasset profile

Views 🔀

Atlan maps views from Cube to its CubeView asset type. A view exposes a curated selection of members drawn from one or more cubes; it's the anchor for intra-model lineage.

Source propertyAtlan propertyWhere in Atlan
View namenameasset profile and overview sidebar
View descriptiondescriptionasset profile and overview sidebar
Parent data sourcecubeDataSource (relationship)asset profile—links back to the CubeDataSource
Count of dimensionscubeDimensionCountasset profile
Count of measurescubeMeasureCountasset profile
Count of segmentscubeSegmentCountasset profile

Dimensions 🔀

Atlan maps dimensions from Cube to its CubeDimension asset type. Dimensions are the members you slice metrics by.

Source propertyAtlan propertyWhere in Atlan
Dimension namenameasset profile and overview sidebar
Dimension descriptiondescriptionasset profile and overview sidebar
Dimension type (for example, string, time, number)semanticTypeasset profile
Whether the dimension is the primary keycubeIsPrimaryKeyasset profile
Upstream column the dimension maps tosemanticExpressionasset profile
Position within its parentcubeMemberOrderasset profile
Parent cube or viewcubeCube / cubeView (relationship)asset profile

Measures 🔀

Atlan maps measures from Cube to its CubeMeasure asset type. Measures are the numeric metrics defined once in the model.

Source propertyAtlan propertyWhere in Atlan
Measure namenameasset profile and overview sidebar
Measure descriptiondescriptionasset profile and overview sidebar
Semantic type (measures resolve to number)semanticTypeasset profile
Position within its parentcubeMemberOrderasset profile
Parent cube or viewcubeCube / cubeView (relationship)asset profile

Segments 🔀

Atlan maps segments from Cube to its CubeSegment asset type. Segments are the named boolean filters defined in the model.

Source propertyAtlan propertyWhere in Atlan
Segment namenameasset profile and overview sidebar
Segment descriptiondescriptionasset profile and overview sidebar
Semantic type (segments resolve to boolean)semanticTypeasset profile
Position within its parentcubeMemberOrderasset profile
Parent cube or viewcubeCube / cubeView (relationship)asset profile

Lineage

Atlan emits lineage as Process entities at crawl time:

  • Warehouse → Cube. For each cube, Atlan reads the warehouse tables the cube is built on and emits a Process from each upstream Table into the CubeCube. For each dimension, measure, and segment, Atlan reads the warehouse column it maps to and emits a Process from the upstream Column into the member. These resolve against the upstream warehouse connection already cataloged in Atlan, matched by the connector type, database, schema, table, and column that Cube's data-source metadata exposes.
  • Cube → View. When a view is built on a cube, Atlan emits a Process from the CubeCube into the CubeView, and from each source cube member into the corresponding view member.

Warehouse lineage is only emitted when Cube's data sources expose the database name for each connection and the corresponding warehouse connection has already been crawled in Atlan. If either is missing, Cube metadata still catalogs cleanly but the warehouse → Cube Process edges are absent.

Warehouse sources supported for lineage

Cube builds its semantic model on an upstream data source. Atlan resolves warehouse → Cube lineage for the following sources—each is supported by Cube as a data source and has a native Atlan connector to resolve against. Crawl the upstream connection in Atlan first so its Table and Column assets exist when the Cube crawl runs.

Cube data sourceAtlan connector
SnowflakeSnowflake
Google BigQueryGoogle BigQuery
Amazon RedshiftAmazon Redshift
DatabricksDatabricks
ClickHouseClickHouse
Amazon AthenaAmazon Athena
PostgreSQLPostgreSQL
MySQLMySQL
Microsoft SQL ServerMicrosoft SQL Server
OracleOracle
Trino (including Starburst)Trino
PrestoPresto
HiveHive
MongoDBMongoDB

Cube can also connect to sources that Atlan catalogs through additional connectors—Dremio, SAP HANA, CrateDB, and Azure Cosmos DB—and lineage resolves for these when Cube reports a matching connector type.