Skip to content

Commit 020a8be

Browse files
authored
Update analytical-store-introduction.md
1 parent c5e0fd0 commit 020a8be

File tree

1 file changed

+11
-9
lines changed

1 file changed

+11
-9
lines changed

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

Lines changed: 11 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -173,21 +173,23 @@ df = spark.read\
173173

174174
* Azure Synapse Spark now supports properties with whitespaces in their names.
175175

176-
### Schema representation
176+
### Schema representation types
177177

178-
There are two modes of schema representation in the analytical store. These modes define the schema representation method for all containers in the database account and have tradeoffs between the simplicity of query experience versus the convenience of a more inclusive columnar representation for polymorphic schemas.
178+
There are two types of schema representation in the analytical store. These types define the schema representation method for all containers in the database account and have tradeoffs between the simplicity of query experience versus the convenience of a more inclusive columnar representation for polymorphic schemas.
179179

180180
* Well-defined schema representation, default option for SQL (CORE) API accounts.
181181
* Full fidelity schema representation, default option for Azure Cosmos DB API for MongoDB accounts.
182182

183-
It is possible to use Full Fidelity Schema for SQL (Core) API accounts. Here are the considerations about this possibility:
183+
#### Full fidelity schema for SQL API accounts
184184

185-
* This option is only valid for accounts that don't have Synapse Link enabled.
186-
* It is not possible to turn Synapse Link off and on again, to reset the default option and change from well-defined to full fidelity.
187-
* It is not possible to change from well-defined to full fidelity using any other process.
188-
* MongoDB accounts are not compatible with this possibility of changing the method of representation.
189-
* Currently this decision cannot be made through the Azure portal.
190-
* The decision on this option should be made at the same time that Synapse Link is enabled on the account:
185+
It is possible to use Full Fidelity Schema for SQL (Core) API accounts, instead of the default option, by setting the schema type when enabling Synapse Link on a Cosmos DB account for the first time. Here are the considerations about changing the default schema representation type:
186+
187+
* This option is only valid for accounts that **don't** have Synapse Link already enabled.
188+
* It is not possible to reset the schema representation type, from well-defined to full fidelity or vice-versa.
189+
* Currently Azure Cosmos DB API for MongoDB accounts are not compatible with this possibility of changing the schema representation. All MongoDB accounts will always have full fidelity schema representation type.
190+
* Currently this change can't be made through the Azure portal. All database accounts that have Synapse LinK enabled by the Azure portal will have the default schema representation type, well defined schema.
191+
192+
The schema representation type decision must be made at the same time that Synapse Link is enabled on the account, using Azure CLI or PowerShell.
191193

192194
With the Azure CLI:
193195
```cli

0 commit comments

Comments
 (0)