DOCSP-14130 Guidance on consistency when querying an ADL (#126)

* DOCSP-14130 Guidance on consistency when querying an ADL

* DOCSP-14130 updates for review feedback

* DOCSP-14130 updates for copy review feedback

Author: kanchana-mongodb

source/query/query-data-lake.txt

@@ -12,29 +12,31 @@ Querying Your Data Lake
    :depth: 2
    :class: singlecol 
 
+You can use the MongoDB Query Language (MQL) on {+adl+} to query and 
+analyze data on your data store. {+adl+} supports most, but not all the 
+standard server commands. To learn more about the supported and 
+unsupported MongoDB server commands and aggregation pipleline stages, 
+see :ref:`data-lake-mql-support`.
+
 You can run up to 30 simultaneous queries on your {+dl+} against:
 
 - Data in your |s3| bucket.
 - Documents in your MongoDB |service| cluster.
 - Data in files hosted at publicly accessible |url|\s.
 
-.. seealso:: 
+.. see:: 
 
    - :doc:`How to Connect to Your Data Lake </tutorial/connect>`
-   - :doc:`How to Run Queries Against Your Data Lake </tutorial/run-queries>`
+   - :doc:`How to Run Queries Against Your Data Lake 
+     </tutorial/run-queries>`
 
 .. _query-s3:
 
 Querying Data on S3 
 -------------------
 
-You can use {+adl+} to query and analyze data on your cloud object store 
-using MongoDB Query Language (MQL). {+adl+} supports most, but not all the 
-standard server commands. To learn more about the supported and unsupported 
-MongoDB server commands and aggregation pipleline stages, see 
-:ref:`data-lake-mql-support`.  
-
-To query data on |s3|, your {+dl+} storage :ref:`configuration 
+You can use {+adl+} to query and analyze data on your cloud object 
+store. To query data on |s3|, your {+dl+} storage :ref:`configuration 
 <datalake-configuration-file>` must contain settings that define:
 
 - Your |s3| {+data-lake-store+}. 
@@ -75,34 +77,37 @@ To query data on |s3|, your {+dl+} storage :ref:`configuration
         ]
       }
 
-To learn more about these settings, see :ref:`datalake-configuration-file`.
+To learn more about these settings, see 
+:ref:`datalake-configuration-file`.
+
+{+dl+} creates the virtual databases and collections you specified in 
+your {+dl+} configuration for the data in your |s3| store. When you 
+:doc:`connect </tutorial/connect>` to your {+dl+} and :doc:`run queries 
+</tutorial/run-queries>`, {+dl+} processes your queries against the 
+data and returns the query results.
 
-{+dl+} creates the virtual databases and collections you specified in your 
-{+dl+} configuration for the data in your |s3| store. When you :doc:`connect 
-</tutorial/connect>` to your {+dl+} and :doc:`run queries 
-</tutorial/run-queries>`, {+dl+} processes your queries against the data and 
-returns the query results.
+When :doc:`deploying </tutorial/deploy>` your {+dl+}, if you specified 
+an |s3| bucket with both read and write permissions or |aws| |s3| 
+:aws:`s3:PutObject </AmazonS3/latest/dev/using-with-s3-actions.html#using-with-s3-actions-related-to-objects>` 
+permission, you can also save your query results in your |s3| bucket 
+using :ref:`adl-out-stage` to |s3|.
 
-When :doc:`deploying </tutorial/deploy>` your {+dl+}, if you specified an |s3| 
-bucket with both read and write permissions or |aws| |s3| :aws:`s3:PutObject 
-</AmazonS3/latest/dev/using-with-s3-actions.html#using-with-s3-actions-related-to-objects>` 
-permission, you can also save your query results in your |s3| bucket using 
-:ref:`adl-out-stage` to |s3|.
+If you successfully create or update an object on your |s3| data store, 
+{+dl+} returns the latest version of that object for any subsequent 
+read requests and all list operations of the objects also reflect the 
+changes. If your query contains multiple stages, each stage receives 
+the most recent data available from the data store as that stage is 
+processed.
 
 .. _query-atlas:
 
 Querying Data in Your |service| Cluster 
 ---------------------------------------
 
-You can use {+adl+} to query and analyze data in your |service| cluster using 
-MongoDB Query Language (MQL). {+adl+} supports most, but not all the standard 
-server commands. To learn more about the supported and unsupported MongoDB 
-server commands and aggregation pipleline stages, see 
-:ref:`data-lake-mql-support`.
-
-To query data in your |service| cluster, your {+dl+} storage 
-:ref:`configuration <datalake-configuration-file>` must contain settings that 
-define: 
+You can use {+adl+} to query and analyze data in your |service| 
+cluster. To query data in your |service| cluster, your {+dl+} storage 
+:ref:`configuration <datalake-configuration-file>` must contain 
+settings that define: 
 
 - Your |service| {+data-lake-store+}.
 - {+dl+} virtual databases and collections that map to your 
@@ -140,19 +145,21 @@ define:
         ]
       }
 
-To learn more about these settings, see :ref:`datalake-configuration-file`. 
+To learn more about these settings, see 
+:ref:`datalake-configuration-file`. 
 
-{+dl+} automatically detects the file format and creates the virtual databases 
-and collections you specified in your {+dl+} configuration. When you 
-:doc:`connect </tutorial/connect>` to your {+dl+} and run queries, {+dl+} 
-processes your queries against the data and returns the query results. 
+{+dl+} automatically detects the file format and creates the virtual 
+databases and collections you specified in your {+dl+} configuration. 
+When you :doc:`connect </tutorial/connect>` to your {+dl+} and run 
+queries, {+dl+} processes your queries against the data and returns the 
+query results. 
 
-If you query a collection in {+adl+} that is mapped to only one |service| 
-collection, {+adl+} acts as a proxy and forwards your query to |service|. 
-When acting as a proxy, {+adl+} doesn't scan data into its virtual collection 
-to proces the query thus improving performance and reducing cost. This 
-optimization is not available for queries on {+adl+} collections that are 
-mapped to multiple |service| collections. 
+If you query a collection in {+adl+} that is mapped to only one 
+|service| collection, {+adl+} acts as a proxy and forwards your query 
+to |service|. When acting as a proxy, {+adl+} doesn't scan data into 
+its virtual collection to proces the query thus improving performance 
+and reducing cost. This optimization is not available for queries on 
+{+adl+} collections that are mapped to multiple |service| collections. 
 
 .. example:: 
 
@@ -203,31 +210,37 @@ mapped to multiple |service| collections.
         ]
       }
 
-   For the above storage configuration, {+adl+} acts as a proxy for queries 
-   on ``foo`` collection and forwards the queries to |service|. This 
-   performance and cost optimization is not available for queries on ``barbaz`` 
-   collection because ``barbaz`` is mapped to multiple |service| collections.
+   For the above storage configuration, {+adl+} acts as a proxy for 
+   queries on ``foo`` collection and forwards the queries to |service|. 
+   This performance and cost optimization is not available for queries 
+   on ``barbaz`` collection because ``barbaz`` is mapped to multiple 
+   |service| collections.
+
+You can also save your query results in your |service| cluster using 
+:ref:`adl-out-stage` to |service|.
+
+If you successfully create or update a document in your collection on 
+the |service| cluster, {+dl+} returns the latest version of that 
+document for any subsequent read requests and all list operations of 
+the collection also reflect the changes. If your query contains 
+multiple stages, each stage receives the most recent data available 
+from the data store as that stage is processed.
 
 .. _query-http:
 
-Querying Data at a |http| |url| 
--------------------------------
+Querying Data at a |http| or |https| |url| 
+------------------------------------------
 
 .. include:: /includes/extracts/fact-http-beta-message.rst
 
-You can use {+adl+} to query and analyze data in files hosted at publicly 
-accessible |url|\s using MongoDB Query Language (MQL). To learn more about the 
-supported data formats, see :ref:`data-lake-data-formats`. {+adl+} supports 
-most, but not all the standard server commands. To learn more about the 
-supported and unsupported MongoDB server commands and aggregation pipleline 
-stages, see :ref:`data-lake-mql-support`. 
-
-To query data in your publicly accessible |url|\s, your {+dl+} storage 
-:ref:`configuration <datalake-configuration-file>` must contain settings that 
-define: 
+You can use {+adl+} to query and analyze data in files hosted at 
+publicly accessible |url|\s. To query data in your publicly accessible 
+|url|\s, your {+dl+} storage :ref:`configuration 
+<datalake-configuration-file>` must contain settings that define: 
 
 - Your |http| {+data-lake-store+}.
-- {+dl+} virtual databases and collections that map to your {+data-lake-store+}.
+- {+dl+} virtual databases and collections that map to your 
+  {+data-lake-store+}.
 
 .. example::
 
@@ -263,27 +276,29 @@ define:
         ]
       }
 
-To learn more about these settings, see :ref:`datalake-configuration-file`. 
+To learn more about these settings, see 
+:ref:`datalake-configuration-file`. 
 
-{+dl+} creates the virtual databases and collections you specified in your 
-{+dl+} configuration for the data in your |url|. {+dl+} also creates one 
-partition for each |url| in your collection. When you :doc:`connect 
-</tutorial/connect>` to your {+dl+} and run queries, {+dl+} processes your 
-queries against the data and returns the query results.
+{+dl+} creates the virtual databases and collections you specified in 
+your {+dl+} configuration for the data in your |url|. {+dl+} also 
+creates one partition for each |url| in your collection. When you 
+:doc:`connect </tutorial/connect>` to your {+dl+} and run queries, 
+{+dl+} processes your queries against the data and returns the query 
+results.
 
 .. _federated-queries:
 
 Running Federated Queries 
 -------------------------
 
 You can use {+adl+} to query and analyze a unified view of data in your 
-|service| cluster, |s3| bucket, and at your |http| URL. For federated queries, 
-your {+dl+} storage :ref:`configuration <datalake-configuration-file>` must 
-contain the settings that define: 
+|service| cluster, |s3| bucket, and at your |http| URL. For federated 
+queries, your {+dl+} storage :ref:`configuration 
+<datalake-configuration-file>` must contain the settings that define: 
 
 - Your |s3|, |service|, and |http| {+data-lake-stores+}.
-- {+dl+} virtual databases and collections that map to your |s3|, |service|, 
-  and |http| {+data-lake-store+}\s.
+- {+dl+} virtual databases and collections that map to your |s3|, 
+  |service|, and |http| {+data-lake-store+}\s.
 
 .. example:: 
 
@@ -342,12 +357,13 @@ contain the settings that define:
         ]
       }
 
-To learn more about these settings, see :ref:`datalake-configuration-file`.
+To learn more about these settings, see 
+:ref:`datalake-configuration-file`.
 
-When you :doc:`connect </tutorial/connect>` to your {+dl+} and run federated
-queries, {+dl+} combines data from your |service| cluster and |s3| bucket 
-in virtual databases and collections and returns a union of data in the 
-results. 
+When you :doc:`connect </tutorial/connect>` to your {+dl+} and run 
+federated queries, {+dl+} combines data from your |service| cluster, 
+|s3| bucket, and |http| store in virtual databases and collections and 
+returns a union of data in the results. 
 
 .. toctree::
    :titlesonly: