Skip to content

Commit c668230

Browse files
Merge pull request #281132 from Rodrigossz/main
Update analytical-store-introduction.md
2 parents 0cb80d8 + f24a9bc commit c668230

File tree

1 file changed

+5
-0
lines changed

1 file changed

+5
-0
lines changed

articles/cosmos-db/analytical-store-introduction.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -487,6 +487,11 @@ FROM OPENROWSET('CosmosDB',
487487
                HTAP) WITH (_id VARCHAR(1000)) as HTAP
488488
```
489489
490+
##### Working with MongoDB `id` field
491+
492+
The `id` property in MongoDB containers is automatically overridden with the Base64 representation of the "_id" property both in analytical store. The "id" field is intended for internal use by MongoDB applications. Currently, the only workaround is to rename the "id" property to something other than "id".
493+
494+
490495
#### Full fidelity schema for API for NoSQL or Gremlin accounts
491496
492497
It's possible to use full fidelity Schema for API for NoSQL accounts, instead of the default option, by setting the schema type when enabling Synapse Link on an Azure Cosmos DB account for the first time. Here are the considerations about changing the default schema representation type:

0 commit comments

Comments
 (0)