Qe cleanup from master (#3297)

* Cleaned up snooty toml

* Removed QE content from release notes, compatibility file, removed 7.0 content from manage-collections.txt

* Removed 7.0 compatibility file from upgrade replacement strings

Author: nvillahermosa-mdb

snooty.toml

@@ -262,9 +262,6 @@ csfle = "Client-Side Field Level Encryption"
 csfle-abbrev = "CSFLE"
 qe = "Queryable Encryption"
 qe-abbr = ":abbr:`QE (Queryable Encryption)`"
-qe-preview = "{+qe+} Public Preview"
-qe-framework = "{+qe+} framework"
-qe-equality-ga = "{+qe-framework+} with equality search"
 in-use-doc = "document with encrypted fields"
 in-use-doc-title = "Document with Encrypted Fields"
 in-use-docs = "documents with encrypted fields"
@@ -335,23 +332,24 @@ targets = [
     "core/queryable-encryption/*/*.txt",
 ]
 
-variant = "warning"
+variant = "danger"
 value = """
-    The {+qe-equality-ga+} is generally available (GA) in \
-    MongoDB 7.0 and later. Data encrypted using the {+qe-preview+} \ 
-    from earlier versions is incompatible with the GA. \
-    For more information, see :ref:`7.0-compatibility`.
+    Queryable Encryption is in Public Preview and available for \
+    evaluation purposes. Public Preview is not recommended for \
+    production deployments as breaking changes may be introduced. \
+    To learn more about the Preview please see the \
+    `Queryable Encryption Preview <https://www.mongodb.com/blog/post/mongodb-releases-queryable-encryption-preview/>`__ \
+    blog post.
     """
 
 [[banners]]
 targets = ["core/csfle.txt", "core/csfle/*.txt", "core/csfle/*/*.txt"]
 
 variant = "tip"
 value = """
-    {+qe-equality-ga+} is now available. \
-    To learn more, see :ref:`qe-manual-feature-qe`.
+    The next-generation Queryable Encryption feature is now in Public Preview. \
+    To learn more about Queryable Encryption, see :ref:`qe-manual-feature-qe`.
     """
-
 [bundle]
 manpages = "manpages.tar.gz"
 

source/core/queryable-encryption/fundamentals/manage-collections.txt

@@ -12,14 +12,8 @@ Encrypted Collection Management
    :depth: 2
    :class: singlecol
 
-It is important that you understand the performance and storage costs of field level encryption. Each encrypted field:
-
-- Adds adds writes to insert, update, and delete operations.
-- Requires additional storage, because MongoDB maintains an encrypted field index.
-
-This section lists the writes per operation and explains how to compact
-encrypted collection indexes so that you can minimize write and storage
-costs.
+In this guide, you can learn how to manage your encrypted collections,
+and the storage and write costs of {+qe+}.
 
 Overview
 --------
@@ -30,9 +24,9 @@ fields.
 
 With {+qe+}, a given plaintext value always encrypts to a different
 ciphertext, while still remaining queryable. To enable
-this functionality, {+qe+} uses three data structures:
+this functionality, {+qe+} uses four data structures:
 
-- Two metadata collections
+- Three metadata collections
 - A field in every document in the encrypted collection called ``__safeContent__``
 
 .. important::
@@ -43,10 +37,11 @@ this functionality, {+qe+} uses three data structures:
 Metadata Collections
 --------------------
 
-When you create an encrypted collection, MongoDB creates two
+When you create an encrypted collection using {+qe+}, MongoDB creates three
 metadata collections:
 
 - ``enxcol_.<collectionName>.esc``, referred to as ``ESC``
+- ``enxcol_.<collectionName>.ecc``, referred to as ``ECC``
 - ``enxcol_.<collectionName>.ecoc``, referred to as ``ECOC``
 
 .. example::
@@ -55,25 +50,29 @@ metadata collections:
    following metadata collections:
 
    - ``enxcol_.patients.esc``
+   - ``enxcol_.patients.ecc``
    - ``enxcol_.patients.ecoc``
 
 
-When you insert documents with a queryable encrypted field,
+When you insert documents with encrypted fields that you wish to query on,
 MongoDB updates the metadata collections to maintain an index
-that enables querying. The field becomes an "indexed field". This
-comes at a cost in storage and write speed for every such field.
+that enables you to query. MongoDB refers to this as "indexed field". This
+comes at a cost in storage and write speed.
 
 Storage Costs
 -------------
 
 Storage and write costs increase based on the number of indexed fields
 per document.
 
-.. important::
+.. important:: Technical Preview
 
-   Expect a {+qe+} collection to have 2-3 times the storage requirements
-   of the documents, to account for metadata collections. For example, a
-   1 GB collection may have a storage requirement of 2-3 GB.
+   MongoDB's guidance during the technical preview is to expect two to
+   three times the storage requirement for a {+qe+} collection and
+   associated metadata collections. For example, a 1 GB collection may
+   have a storage requirement of 2-3 GB for associated metadata collections.
+
+   This guidance will be tuned in a future release.
 
 Write Costs
 -----------
@@ -98,10 +97,11 @@ metadata collections.
 Update Operations
 ~~~~~~~~~~~~~~~~~
 
-When updating a document, each indexed field requires three writes to
+When updating a document, each indexed field requires four writes to
 metadata collections.
 
 - One write to ``ESC``
+- One write to ``ECC``
 - Two writes to ``ECOC``
 
 
@@ -110,44 +110,45 @@ metadata collections.
    Updating a document with two indexed fields requires:
 
    - One write to the encrypted collection.
-   - Six writes to the metadata collections.
+   - Eight writes to the metadata collections.
 
 
 Delete Operations
 ~~~~~~~~~~~~~~~~~
 
-When deleting a document, each indexed field requires one write to the
+When deleting a document, each indexed field requires two writes to the
 metadata collections.
 
+- One write to ``ECC``
 - One write to ``ECOC``
 
 
 .. example::
 
    Deleting a document with two indexed fields requires:
 
-   - One write to the encrypted collection.
-   - Two writes to the metadata collections.
+   - One write into the encrypted collection.
+   - Four writes to the metadata collections.
 
 
 .. _qe-index-compaction:
 
 Index Compaction
 ----------------
 
-As you insert, update, and delete documents, the metadata collections
-change and grow. Index compaction prunes the metadata collections and 
-reduces their size.
+.. important:: Technical Preview
 
-.. important::
+   You are required to run index compaction during the technical preview.
+   MongoDB plans to automatically run index compaction in a future release.
 
-   You must manually run index compaction. Compaction only works on
-   clients configured for {+qe+}.
+As you insert, update, and delete documents, the metadata collections
+change and grow. Index compaction is a process that prunes the metadata
+collections and reduces their size.
 
-Run index compaction when the size of ``ECOC`` exceeds 1 GB.
+You should run index compaction when the size of ``ECOC`` exceeds 1 GB.
 
 You can check the size of your collections using :binary:`~bin.mongosh`
-and issuing the :method:`db.collection.totalSize()` command.
+and issuing the ``db.collection.totalSize()`` command.
 
 .. example::
 
@@ -165,6 +166,10 @@ and issuing the :method:`db.collection.totalSize()` command.
 
         1407960328
 
+.. important::
+
+   You must configure your client for {+qe+} to run index compaction.
+
 To run index compaction, use :binary:`~bin.mongosh` and run the
 ``db.collection.compactStructuredEncryptionData()`` command to reduce
 the size of the metadata collections.

source/core/queryable-encryption/reference/limitations.txt

@@ -1,8 +1,8 @@
 .. _qe-reference-encryption-limits:
 
-================================
-{+qe+} Limitations
-================================
+===========
+Limitations
+===========
 
 .. default-domain:: mongodb
 

source/includes/7.0-upgrade-replacements.rst

@@ -3,7 +3,6 @@
 .. |oldversion| replace:: 6.0
 .. |oldseries| replace:: 6.0-series
 .. |olderseries| replace:: 5.0-series
-.. |compatibility| replace:: :ref:`7.0-compatibility`
 .. |upgradefirst| replace:: :ref:`upgrade first to 6.0 <6.0-upgrade>`
 .. |downgradepath| replace:: After upgrading to |newversion|, if you need to downgrade, we recommend |downgrading| to the latest patch release of |downgradeversion|.
 

source/release-notes/7.0-compatibility.txt

@@ -191,10 +191,4 @@ remove data that uses any of the following features:
    :titlesonly:
    :hidden:
 
-   /release-notes/7.0-compatibility
-.. toctree::
-   :titlesonly:
-   :hidden:
-   
-   /release-notes/7.0-compatibility
    /release-notes/7.0-upgrade