What does Atlan crawl from Amazon DocumentDB?
This reference document details the Amazon DocumentDB assets and properties that Atlan crawls and maps during metadata extraction. Atlan currently doesn't support lineage for Amazon DocumentDB assets.
Asset model
Amazon DocumentDB is MongoDB-compatible, so Atlan reuses the native MongoDB asset model to catalog DocumentDB metadata. There is no separate DocumentDB-specific asset family. Atlan distinguishes DocumentDB assets from MongoDB assets using the connectorName="documentdb" discriminator on the connection, so assets appear under the DocumentDB connector in the Atlan UI.
Atlan crawls and maps the following asset types from Amazon DocumentDB, in this hierarchy:
- MongoDB Database (database) → MongoDB Collection (collection) → Column (inferred field).
After crawling Amazon DocumentDB, you can use connector-specific filters to discover assets.
The following sections show how each asset type is mapped, including the source metadata and the corresponding Atlan property.
Databases
Atlan maps databases from DocumentDB to its MongoDBDatabase asset type.
| Source metadata | Atlan property |
|---|---|
| Database name | name |
| Number of collections in the database | mongoDBDatabaseCollectionCount |
Collections
Atlan maps collections from DocumentDB to its MongoDBCollection asset type. Collection statistics are derived from collStats.
| Source metadata | Atlan property |
|---|---|
| Collection name | name |
| Parent database name | databaseName |
| Number of inferred fields | columnCount |
collStats.count (document count) | rowCount |
collStats.storageSize | sizeBytes |
collStats.nindexes | mongoDBCollectionNumIndexes |
collStats.totalIndexSize | mongoDBCollectionTotalIndexSize |
collStats.avgObjSize | mongoDBCollectionAverageObjectSize |
collStats.maxSize | mongoDBCollectionMaxSize |
| Inferred schema definition | mongoDBCollectionSchemaDefinition |
Columns
Atlan maps each inferred field from DocumentDB to its Column asset type. Fields are inferred by sampling documents per collection. For details on how field schemas are consolidated and what limitations apply, see How are column schemas consolidated? in the FAQ.
| Source metadata | Atlan property |
|---|---|
| Field name (last path segment) | name |
| Field order within its parent | order |
| Inferred data type (mapped from BSON type) | dataType |
| Raw inferred type definition | rawDataTypeDefinition |
| Parent collection name | nosqlCollectionName |
| Parent column name (for nested fields) | parentColumnName |
| Complete hierarchy from parent column to child column | parentColumnQualifiedName |
| Nesting depth of the field | columnDepthLevel |
nested for fields below the top level | subDataType |
Nested fields are represented using dot-notation qualified names (for example, address.city) and are published up to 3 levels deep. For details, see Are nested fields supported? in the FAQ.