DOCS-16264 Specifies that readConcern for QE sharded transactions must be snapshot (#4076)

sarahsimpers · web-flow · commit 3b091788af5a · 2023-07-20T11:46:15.000-07:00
* DOCS-16264 Specifies that readConcern for QE sharded transactions must be snapshot

* Includes change from copy review

* Includes edit from CB
diff --git a/source/core/queryable-encryption/reference/limitations.txt b/source/core/queryable-encryption/reference/limitations.txt
@@ -137,6 +137,7 @@ Sharding
 
 - Metadata collections must not be sharded
 - Shard keys must not be encrypted fields
+- .. include:: /includes/fact-sharded-transactions-qe-readconcern.rst
 
 CRUD
 ----
diff --git a/source/core/queryable-encryption/reference/supported-operations.txt b/source/core/queryable-encryption/reference/supported-operations.txt
@@ -101,6 +101,8 @@ encryption returns an error.
 
    - Applications without the correct encryption options see the encrypted values.
 
+.. include:: /includes/fact-sharded-transactions-qe-readconcern.rst
+
 .. _qe-supported-query-operators:
 
 Supported Query Operators
diff --git a/source/includes/fact-sharded-transactions-qe-readconcern.rst b/source/includes/fact-sharded-transactions-qe-readconcern.rst
@@ -0,0 +1,2 @@
+For sharded cluster transactions that use Queryable Encryption, you
+must set :ref:`readConcern <read-concern>` to ``snapshot``.

Original file line number	Diff line number	Diff line change
`@@ -0,0 +1,2 @@`
	`1`	`+For sharded cluster transactions that use Queryable Encryption, you`
	`2`	+must set :ref:`readConcern <read-concern>` to ``snapshot``.