Merge pull request MicrosoftDocs#2 from MikeRayMSFT/20210408-spark-streaming

Update to fix issues, and sync from master

Author: MikeRayMSFT

.openpublishing.redirection.json

@@ -42353,6 +42353,11 @@
     {
       "source_path": "docs/advanced-analytics/r/converting-r-code-for-use-in-sql-server.md",
       "redirect_url": "/sql/machine-learning/r/converting-r-code-for-use-in-sql-server",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "docs/machine-learning/r/converting-r-code-for-use-in-sql-server.md",
+      "redirect_url": "/sql/machine-learning/deploy/modify-r-python-code-to-run-in-sql-server",
       "redirect_document_id": true
     },
     {
@@ -42403,6 +42408,11 @@
     {
       "source_path": "docs/advanced-analytics/r/operationalizing-your-r-code.md",
       "redirect_url": "/sql/machine-learning/r/operationalizing-your-r-code",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "docs/machine-learning/r/operationalizing-your-r-code.md",
+      "redirect_url": "/sql/machine-learning/deploy/operationalizing-your-r-code",
       "redirect_document_id": true
     },
     {

docs/azdata/install/deploy-install-azdata-linux-package.md

@@ -4,7 +4,7 @@ description: Learn how to install the Azure Data CLI (azdata) tool with apt.
 author: MikeRayMSFT 
 ms.author: mikeray
 ms.reviewer: mihaelab
-ms.date: 09/30/2020
+ms.date: 04/07/2021
 ms.topic: conceptual
 ms.prod: sql
 ms.technology: big-data-cluster
@@ -16,7 +16,7 @@ ms.technology: big-data-cluster
 
 For Linux distributions with `apt` there is a package for the `azdata-cli`. The CLI package has been tested on Linux versions which use `apt`:
 
-- Ubuntu 16.04, Ubuntu 18.04
+- Ubuntu 16.04, Ubuntu 18.04, Ubuntu 20.04
 
 [!INCLUDE [azdata-package-installation-remove-pip-install](../../includes/azdata-package-installation-remove-pip-install.md)]
 

docs/azdata/reference/reference-azdata-app-template.md

@@ -75,7 +75,7 @@ azdata app template pull --name ssis
 ```
 ### Optional Parameters
 #### `--name -n`
-Template name. For a full list off supported template namesrun `azdata app template list`
+Template name. For a full list off supported template names, run `azdata app template list`
 #### `--url -u`
 Specify a different template repository location. Default: https://github.com/Microsoft/SQLBDC-AppDeploy.git
 #### `--destination -d`

docs/azdata/reference/reference-azdata-arc-dc-config.md

@@ -78,7 +78,7 @@ JMESPath query string. See [http://jmespath.org/](http://jmespath.org) for more
 #### `--verbose`
 Increase logging verbosity. Use --debug for full debug logs.
 ## azdata arc dc config add
-Adds the value at the json path in the config file.  All examples below are given in Bash.  If using another command line, please be aware that you may need to escapequotations appropriately.  Alternatively, you may use the patch file functionality.
+Adds the value at the json path in the config file.  All examples below are given in Bash.  If using another command line, please be aware that you may need to escape quotations appropriately.  Alternatively, you may use the patch file functionality.
 ```bash
 azdata arc dc config add 
 ```
@@ -99,7 +99,7 @@ JMESPath query string. See [http://jmespath.org/](http://jmespath.org) for more
 #### `--verbose`
 Increase logging verbosity. Use --debug for full debug logs.
 ## azdata arc dc config remove
-Removes the value at the json path in the config file.  All examples below are given in Bash.  If using another command line, please be aware that you may need to escapequotations appropriately.  Alternatively, you may use the patch file functionality.
+Removes the value at the json path in the config file.  All examples below are given in Bash.  If using another command line, please be aware that you may need to escape quotations appropriately.  Alternatively, you may use the patch file functionality.
 ```bash
 azdata arc dc config remove 
 ```
@@ -120,7 +120,7 @@ JMESPath query string. See [http://jmespath.org/](http://jmespath.org) for more
 #### `--verbose`
 Increase logging verbosity. Use --debug for full debug logs.
 ## azdata arc dc config replace
-Replaces the value at the json path in the config file.  All examplesbelow are given in Bash.  If using another command line, please be aware that you may need to escapequotations appropriately.  Alternatively, you may use the patch file functionality.
+Replaces the value at the json path in the config file.  All examples below are given in Bash.  If using another command line, please be aware that you may need to escape quotations appropriately.  Alternatively, you may use the patch file functionality.
 ```bash
 azdata arc dc config replace 
 ```

docs/azdata/reference/reference-azdata-arc-postgres-backup.md

@@ -150,7 +150,7 @@ ID of the backup. If not specified, the most recent backup taken will be restore
 #### `--source-server-name -ssn`
 Name of the source Azure Arc enabled PostgreSQL Hyperscale server group. If not provided, the backup will be restored in place on the server group identified by --server-name.
 #### `--time -t`
-The point in time to restore to, given either as a timestamp or a number and suffix (m for minutes, h for hours, d for days, and w for weeks). E.g. 1.5h goes back 90 minutes. If specifed, --source-server-name must be given to restore the backup from a separate Azure Arc enabled PostgreSQL Hyperscale server group.
+The point in time to restore to, given either as a timestamp or a number and suffix (m for minutes, h for hours, d for days, and w for weeks). E.g. 1.5h goes back 90 minutes. If specified, --source-server-name must be given to restore the backup from a separate Azure Arc enabled PostgreSQL Hyperscale server group.
 ### Global Arguments
 #### `--debug`
 Increase logging verbosity to show all debug logs.

docs/azdata/reference/reference-azdata-arc-postgres-server-config.md

@@ -55,7 +55,7 @@ JMESPath query string. See [http://jmespath.org/](http://jmespath.org) for more
 #### `--verbose`
 Increase logging verbosity. Use --debug for full debug logs.
 ## azdata arc postgres server config add
-Adds the value at the json path in the config file.  All examples below are given in Bash.  If using another command line, please be aware that you may need to escapequotations appropriately.  Alternatively, you may use the patch file functionality.
+Adds the value at the json path in the config file.  All examples below are given in Bash.  If using another command line, please be aware that you may need to escape quotations appropriately.  Alternatively, you may use the patch file functionality.
 ```bash
 azdata arc postgres server config add --path -p 
                                       --json-values -j
@@ -82,7 +82,7 @@ JMESPath query string. See [http://jmespath.org/](http://jmespath.org) for more
 #### `--verbose`
 Increase logging verbosity. Use --debug for full debug logs.
 ## azdata arc postgres server config remove
-Removes the value at the json path in the config file.  All examples below are given in Bash.  If using another command line, please be aware that you may need to escapequotations appropriately.  Alternatively, you may use the patch file functionality.
+Removes the value at the json path in the config file.  All examples below are given in Bash.  If using another command line, please be aware that you may need to escape quotations appropriately.  Alternatively, you may use the patch file functionality.
 ```bash
 azdata arc postgres server config remove --path -p 
                                          --json-path -j
@@ -109,7 +109,7 @@ JMESPath query string. See [http://jmespath.org/](http://jmespath.org) for more
 #### `--verbose`
 Increase logging verbosity. Use --debug for full debug logs.
 ## azdata arc postgres server config replace
-Replaces the value at the json path in the config file.  All examplesbelow are given in Bash.  If using another command line, please be aware that you may need to escapequotations appropriately.  Alternatively, you may use the patch file functionality.
+Replaces the value at the json path in the config file.  All examples below are given in Bash.  If using another command line, please be aware that you may need to escape quotations appropriately.  Alternatively, you may use the patch file functionality.
 ```bash
 azdata arc postgres server config replace --path -p 
                                           --json-values -j

docs/azdata/reference/reference-azdata-arc-sql-mi-config.md

@@ -52,7 +52,7 @@ JMESPath query string. See [http://jmespath.org/](http://jmespath.org) for more
 #### `--verbose`
 Increase logging verbosity. Use --debug for full debug logs.
 ## azdata arc sql mi config add
-Adds the value at the json path in the config file.  All examples below are given in Bash.  If using another command line, please be aware that you may need to escapequotations appropriately.  Alternatively, you may use the patch file functionality.
+Adds the value at the json path in the config file.  All examples below are given in Bash.  If using another command line, please be aware that you may need to escape quotations appropriately.  Alternatively, you may use the patch file functionality.
 ```bash
 azdata arc sql mi config add --path -p 
                              --json-values -j
@@ -79,7 +79,7 @@ JMESPath query string. See [http://jmespath.org/](http://jmespath.org) for more
 #### `--verbose`
 Increase logging verbosity. Use --debug for full debug logs.
 ## azdata arc sql mi config remove
-Removes the value at the json path in the config file.  All examples below are given in Bash.  If using another command line, please be aware that you may need to escapequotations appropriately.  Alternatively, you may use the patch file functionality.
+Removes the value at the json path in the config file.  All examples below are given in Bash.  If using another command line, please be aware that you may need to escape quotations appropriately.  Alternatively, you may use the patch file functionality.
 ```bash
 azdata arc sql mi config remove --path -p 
                                 --json-path -j
@@ -106,7 +106,7 @@ JMESPath query string. See [http://jmespath.org/](http://jmespath.org) for more
 #### `--verbose`
 Increase logging verbosity. Use --debug for full debug logs.
 ## azdata arc sql mi config replace
-Replaces the value at the json path in the config file.  All examplesbelow are given in Bash.  If using another command line, please be aware that you may need to escapequotations appropriately.  Alternatively, you may use the patch file functionality.
+Replaces the value at the json path in the config file.  All examples below are given in Bash.  If using another command line, please be aware that you may need to escape quotations appropriately.  Alternatively, you may use the patch file functionality.
 ```bash
 azdata arc sql mi config replace --path -p 
                                  --json-values -j

docs/azdata/reference/reference-azdata-arc-sql-mi.md

@@ -87,7 +87,7 @@ The request for cores of the managed instance as an integer.
 #### `--memory-limit -ml`
 The limit of the capacity of the managed instance as an integer.
 #### `--memory-request -mr`
-The request for the capcity of the managed instance as an integer amount of memory in GBs.
+The request for the capacity of the managed instance as an integer amount of memory in GBs.
 #### `--storage-class-data -scd`
 The storage class to be used for data (.mdf). If no value is specified, then no storage class will be specified, which will result in Kubernetes using the default storage class.
 #### `--storage-class-logs -scl`
@@ -153,7 +153,7 @@ The request for cores of the managed instance as an integer.
 #### `--memory-limit -ml`
 The limit of the capacity of the managed instance as an integer.
 #### `--memory-request -mr`
-The request for the capcity of the managed instance as an integer amount of memory in GBs.
+The request for the capacity of the managed instance as an integer amount of memory in GBs.
 #### `--no-wait`
 If given, the command will not wait for the instance to be in a ready state before returning.
 ### Global Arguments

docs/azdata/reference/reference-azdata-bdc-config.md

@@ -127,7 +127,7 @@ azdata bdc config show --config-file custom-config/bdc.json --json-path "$.spec.
 ```
 ### Optional Parameters
 #### `--config-file -c`
-Big data cluster config file path if you don't want the config of the cluster you are currentlylogged in to, i.e. custom/bdc.json
+Big data cluster config file path if you don't want the config of the cluster you are currently logged in to, i.e. custom/bdc.json
 #### `--target -t`
 Output file to store the result in. Default: directed to stdout.
 #### `--json-path -j`
@@ -146,7 +146,7 @@ JMESPath query string. See [http://jmespath.org/](http://jmespath.org) for more
 #### `--verbose`
 Increase logging verbosity. Use --debug for full debug logs.
 ## azdata bdc config add
-Adds the value at the json path in the config file.  All examples below are given in Bash.  If using another command line, please be aware that you may need to escapequotations appropriately.  Alternatively, you may use the patch file functionality.
+Adds the value at the json path in the config file.  All examples below are given in Bash.  If using another command line, please be aware that you may need to escape quotations appropriately.  Alternatively, you may use the patch file functionality.
 ```bash
 azdata bdc config add --path -p 
                       --json-values -j
@@ -173,7 +173,7 @@ JMESPath query string. See [http://jmespath.org/](http://jmespath.org) for more
 #### `--verbose`
 Increase logging verbosity. Use --debug for full debug logs.
 ## azdata bdc config remove
-Removes the value at the json path in the config file.  All examples below are given in Bash.  If using another command line, please be aware that you may need to escapequotations appropriately.  Alternatively, you may use the patch file functionality.
+Removes the value at the json path in the config file.  All examples below are given in Bash.  If using another command line, please be aware that you may need to escape quotations appropriately.  Alternatively, you may use the patch file functionality.
 ```bash
 azdata bdc config remove --path -p 
                          --json-path -j
@@ -200,7 +200,7 @@ JMESPath query string. See [http://jmespath.org/](http://jmespath.org) for more
 #### `--verbose`
 Increase logging verbosity. Use --debug for full debug logs.
 ## azdata bdc config replace
-Replaces the value at the json path in the config file.  All examplesbelow are given in Bash.  If using another command line, please be aware that you may need to escapequotations appropriately.  Alternatively, you may use the patch file functionality.
+Replaces the value at the json path in the config file.  All examples below are given in Bash.  If using another command line, please be aware that you may need to escape quotations appropriately.  Alternatively, you may use the patch file functionality.
 ```bash
 azdata bdc config replace --path -p 
                           --json-values -j

docs/big-data-cluster/spark-streaming-guide.md

@@ -1,5 +1,5 @@
 ---
-title: SQL Server Big Data Clusters Spark Streaming Guide
+title: SQL Server Big Data Clusters Spark streaming guide
 titleSuffix: SQL Server Big Data Clusters
 description: This guide covers streaming use cases and how to implement it using SQL Server Big Data Clusters capabilities.
 author: dacoelho 
@@ -12,11 +12,11 @@ ms.prod: sql
 ms.technology: big-data-cluster
 ---
 
-# SQL Server Big Data Clusters Spark Streaming Guide
+# SQL Server Big Data Clusters Spark streaming guide
 
 [!INCLUDE[SQL Server 2019](../includes/applies-to-version/sqlserver2019.md)]
 
-This guide covers streaming use cases and how to implement it using SQL Server Big Data Clusters Spark. 
+This guide covers streaming use cases and how to implement it using SQL Server Big Data Clusters Spark.
 
 In this guide, you'll learn how to:
 
@@ -34,9 +34,9 @@ In this guide, you'll learn how to:
 This guide assumes good level of understanding of streaming technology concepts and architectures.
 The following articles provide excellent conceptual baselines:
 
-* [Data Architecture Guide - Real time processing](https://docs.microsoft.com/azure/architecture/data-guide/big-data/real-time-processing)
-* [Use Azure Event Hubs from Apache Kafka applications](https://docs.microsoft.com/azure/event-hubs/event-hubs-for-kafka-ecosystem-overview)
-* [Data Architecture Guide - Choosing a real-time message ingestion technology in Azure](https://docs.microsoft.com/azure/architecture/data-guide/technology-choices/real-time-ingestion)
+* [Data Architecture Guide - Real time processing](/azure/architecture/data-guide/big-data/real-time-processing)
+* [Use Azure Event Hubs from Apache Kafka applications](/azure/event-hubs/event-hubs-for-kafka-ecosystem-overview)
+* [Data Architecture Guide - Choosing a real-time message ingestion technology in Azure](/azure/architecture/data-guide/technology-choices/real-time-ingestion)
 
 ### Apache Kafka and Azure Event Hub conceptual mapping
 
@@ -50,7 +50,7 @@ The following articles provide excellent conceptual baselines:
 
 ### Reproducibility
 
-This guide leverages the producer application provided by the [Quickstart: Data streaming with Event Hubs using the Kafka protocol](https://docs.microsoft.com/azure/event-hubs/event-hubs-quickstart-kafka-enabled-event-hubs). Furthermore, there are sample applications in many programming languages on [Azure Event Hubs for Apache Kafka GitHub](https://github.com/Azure/azure-event-hubs-for-kafka) page to help you jumpstart streaming scenarios.
+This guide leverages the producer application provided by the [Quickstart: Data streaming with Event Hubs using the Kafka protocol](/azure/event-hubs/event-hubs-quickstart-kafka-enabled-event-hubs). Furthermore, there are sample applications in many programming languages on [Azure Event Hubs for Apache Kafka GitHub](https://github.com/Azure/azure-event-hubs-for-kafka) page to help you jumpstart streaming scenarios.
 
 Here is a modified `producer.py` that streams simulated sensor JSON data into Streaming engine using a Kafka compatible client. It is important to notice that Azure Event Hubs is Kafka protocol compatible. Follow the setup instructions in the [GitHub repository](https://github.com/Azure/azure-event-hubs-for-kafka/tree/master/quickstart/python) to get the sample to work for you. The `conf` dictionary is where all connection information takes place and your mileage may vary depending on your environment. Make sure you replace at least `bootstrap.servers` and `sasl.password` as it is the most relevant configuration in the code sample bellow.