DOCSP-11807 doc for http store (#60)

* DOCSP-11807 doc for http store

* DOCSP-11807 updates for copy review feedback

* DOCSP-11807 updates for tech review feedback

* DOCSP-11807 updates for tech review feedback

* DOCSP-11807 updates for PM feedback

* DOCSP-11807 minor fix

Author: kanchana-mongodb

source/admin/query-with-sql.txt

@@ -6,7 +6,7 @@ Querying with SQL
 
 .. default-domain:: mongodb
 
-.. include:: /includes/fact-sql-beta-message.rst
+.. include:: /includes/extracts/fact-sql-beta-message.rst
 
 {+adl+} supports SQL format queries through the :ref:`JDBC driver 
 <jdbc-driver>` for {+adl+} and using the :ref:`adl-sql-stage` 

source/includes/extracts-beta-message.yaml

@@ -0,0 +1,18 @@
+ref: fact-sql-beta-message
+content: |
+
+  .. note:: Beta
+
+     The support for SQL format queries is available as a Beta feature. 
+     The feature and the corresponding documentation may change at any 
+     time during the Beta stage. 
+---
+ref: fact-http-beta-message
+content: |
+
+  .. note:: Beta
+
+     The support for HTTP data stores is available as a Beta feature. 
+     The feature and the corresponding documentation may change at any 
+     time during the Beta stage. 
+...

source/includes/extracts-common-conf-params.yaml

@@ -0,0 +1,43 @@
+ref: param-default-format
+content: |
+
+  .. datalakeconf:: databases.[n].collections.[n].dataSources.[n].defaultFormat
+
+     *Optional.* Specifies the default format {+data-lake-short+} assumes
+     if it encounters a file without an extension while searching the
+     :datalakeconf:`~databases.[n].collections.[n].dataSources.[n].storeName`.
+   
+     If omitted, {+data-lake-short+} attempts to detect the file type by 
+     processing a few bytes of the file.
+   
+     .. note::
+   
+        If your file format is ``CSV`` or ``TSV``, you must include a header 
+        row in your data. See :ref:`data-lake-csv-tsv-data` for more 
+        information.
+      
+     The following values are valid for the ``defaultFormat`` field:
+      
+     ``.json, .json.gz, .bson, .bson.gz, .avro, .avro.gz, .orc, .tsv, .tsv.gz, 
+     .csv, .csv.gz, .parquet``
+
+     .. seealso:: 
+
+        :ref:`data-lake-data-formats`
+---
+ref: cli-param-collection-name
+content: |
+  Either the name of the collection to which {+data-lake-short+} maps the data 
+  contained in the {+data-lake-store+} or the wildcard ``"*"`` to dynamically 
+  create collections. 
+---
+ref: cli-param-default-format
+content: | 
+  The format that {+data-lake-short+} defaults to if it encounters a file 
+  without an extension while querying the {+data-lake-store+}. If omitted, 
+  {+data-lake-short+} attempts to detect the file type by processing a few 
+  bytes of the file. The following values are valid: 
+   
+  ``.json, .json.gz, .bson, .bson.gz, .avro, .avro.gz, .orc, .tsv, .tsv.gz, 
+  .csv, .csv.gz, .parquet``
+...

source/includes/fact-sql-beta-message.rst

@@ -138,11 +138,70 @@ define:
 
 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 |service| cluster. When you 
+{+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 against the data and returns the query 
-results.
+processes your queries against the data and returns the query results.
+
+.. _query-http:
+
+Querying Data at a |http| |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: 
+
+- Your |http| {+data-lake-store+}.
+- {+dl+} virtual databases and collections that map to your {+data-lake-store+}.
+
+.. example::
+
+   .. code-block:: json
+
+      {
+        "stores" : [
+          {
+            "name" : "<store-name>",
+            "provider": "http",
+            "urls": ["<url>"]
+          }
+        ],
+        "databases" : [
+          {
+            "name" : "<database-name>",
+            "collections" : [
+              {
+                "name" : "<collection-name>",
+                "dataSources" : [
+                  {
+                    "storeName" : "<store-name>",
+                    "defaultFormat" : "<file-format>",
+                    "urls" : ["<url>"]
+                  }
+                ]
+              }
+            ]
+          }
+        ]
+      }
+
+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.
 
 .. _federated-queries: