## What does Atlan crawl from Cube?

URL: https://docs.atlan.com/apps/connectors/semantic-layer/cube/references/what-does-atlan-crawl-from-cube

> During a Cube crawl, Atlan extracts your semantic model—data sources, cubes, views, dimensions, measures, and segments—and maps each property to its Atlan asset. Reference tables and lineage below.

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 property | Atlan property | Where in Atlan |
| --- | --- | --- |
| Environment name | `name` | asset profile and overview sidebar |
| Deployment id | `deploymentId` | asset profile |
| Environment id | `environmentId` | asset profile |
| Environment type (for example, `production`) | `environmentType` | asset profile |
| Environment branch | `environmentBranch` | asset profile |
| Count of cubes in the model | `cubeCubeCount` | asset profile |
| Count of views in the model | `cubeViewCount` | asset 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 property | Atlan property | Where in Atlan |
| --- | --- | --- |
| Cube name | `name` | asset profile and overview sidebar |
| Cube description | `description` | asset profile and overview sidebar |
| Parent data source | `cubeDataSource` (relationship) | asset profile—links back to the `CubeDataSource` |
| Count of dimensions | `cubeDimensionCount` | asset profile |
| Count of measures | `cubeMeasureCount` | asset profile |
| Count of segments | `cubeSegmentCount` | asset 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 property | Atlan property | Where in Atlan |
| --- | --- | --- |
| View name | `name` | asset profile and overview sidebar |
| View description | `description` | asset profile and overview sidebar |
| Parent data source | `cubeDataSource` (relationship) | asset profile—links back to the `CubeDataSource` |
| Count of dimensions | `cubeDimensionCount` | asset profile |
| Count of measures | `cubeMeasureCount` | asset profile |
| Count of segments | `cubeSegmentCount` | asset profile |

## Dimensions 🔀

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

| Source property | Atlan property | Where in Atlan |
| --- | --- | --- |
| Dimension name | `name` | asset profile and overview sidebar |
| Dimension description | `description` | asset profile and overview sidebar |
| Dimension type (for example, `string`, `time`, `number`) | `semanticType` | asset profile |
| Whether the dimension is the primary key | `cubeIsPrimaryKey` | asset profile |
| Upstream column the dimension maps to | `semanticExpression` | asset profile |
| Position within its parent | `cubeMemberOrder` | asset profile |
| Parent cube or view | `cubeCube` / `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 property | Atlan property | Where in Atlan |
| --- | --- | --- |
| Measure name | `name` | asset profile and overview sidebar |
| Measure description | `description` | asset profile and overview sidebar |
| Semantic type (measures resolve to `number`) | `semanticType` | asset profile |
| Position within its parent | `cubeMemberOrder` | asset profile |
| Parent cube or view | `cubeCube` / `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 property | Atlan property | Where in Atlan |
| --- | --- | --- |
| Segment name | `name` | asset profile and overview sidebar |
| Segment description | `description` | asset profile and overview sidebar |
| Semantic type (segments resolve to `boolean`) | `semanticType` | asset profile |
| Position within its parent | `cubeMemberOrder` | asset profile |
| Parent cube or view | `cubeCube` / `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 source | Atlan connector |
| --- | --- |
| Snowflake | [Snowflake](https://docs.atlan.com/llms/connectors/snowflake/llms.txt) |
| Google BigQuery | [Google BigQuery](https://docs.atlan.com/llms/connectors/google-bigquery/llms.txt) |
| Amazon Redshift | [Amazon Redshift](https://docs.atlan.com/llms/connectors/amazon-redshift/llms.txt) |
| Databricks | [Databricks](https://docs.atlan.com/llms/connectors/databricks/llms.txt) |
| ClickHouse | [ClickHouse](https://docs.atlan.com/llms/connectors/clickhouse/llms.txt) |
| Amazon Athena | [Amazon Athena](https://docs.atlan.com/llms/connectors/amazon-athena/llms.txt) |
| PostgreSQL | [PostgreSQL](https://docs.atlan.com/llms/connectors/postgresql/llms.txt) |
| MySQL | [MySQL](https://docs.atlan.com/llms/connectors/mysql/llms.txt) |
| Microsoft SQL Server | [Microsoft SQL Server](https://docs.atlan.com/llms/connectors/microsoft-sql-server/llms.txt) |
| Oracle | [Oracle](https://docs.atlan.com/llms/connectors/oracle/llms.txt) |
| Trino (including Starburst) | [Trino](https://docs.atlan.com/llms/connectors/trino/llms.txt) |
| Presto | [Presto](https://docs.atlan.com/llms/connectors/prestosql/llms.txt) |
| Hive | [Hive](https://docs.atlan.com/llms/connectors/hive/llms.txt) |
| MongoDB | [MongoDB](https://docs.atlan.com/apps/connectors/database/mongodb) |

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.

---