Skip to content

Commit 2ae6a69

Browse files
authored
Merge pull request #88669 from dagiro/cats99
cats99
2 parents 5b5ccac + 7857b97 commit 2ae6a69

File tree

4 files changed

+15
-14
lines changed

4 files changed

+15
-14
lines changed

articles/hdinsight/apache-kafka-spark-structured-streaming-cosmosdb.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -37,7 +37,7 @@ Apache Kafka on HDInsight does not provide access to the Kafka brokers over the
3737
While you can create an Azure virtual network, Kafka, and Spark clusters manually, it's easier to use an Azure Resource Manager template. Use the following steps to deploy an Azure virtual network, Kafka, and Spark clusters to your Azure subscription.
3838

3939
1. Use the following button to sign in to Azure and open the template in the Azure portal.
40-
40+
4141
<a href="https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FAzure-Samples%2Fhdinsight-spark-scala-kafka-cosmosdb%2Fmaster%2Fazuredeploy.json" target="_blank">
4242
<img src="./media/apache-kafka-spark-structured-streaming-cosmosdb/resource-manager-deploy.png" alt="Deploy to Azure"/>
4343
</a>
@@ -61,11 +61,11 @@ While you can create an Azure virtual network, Kafka, and Spark clusters manuall
6161
> The structured streaming notebook used in this example requires Spark on HDInsight 3.6. If you use an earlier version of Spark on HDInsight, you receive errors when using the notebook.
6262
6363
2. Use the following information to populate the entries on the **Custom deployment** section:
64-
65-
![HDInsight custom deployment](./media/apache-kafka-spark-structured-streaming-cosmosdb/hdi-custom-parameters.png)
64+
65+
![HDInsight custom deployment values](./media/apache-kafka-spark-structured-streaming-cosmosdb/hdi-custom-parameters.png)
6666

6767
* **Subscription**: Select your Azure subscription.
68-
68+
6969
* **Resource group**: Create a group or select an existing one. This group contains the HDInsight cluster.
7070

7171
* **Location**: Select a location geographically close to you.

articles/hdinsight/connect-on-premises-network.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -35,7 +35,7 @@ This configuration enables the following behavior:
3535

3636
In the following diagram, green lines are requests for resources that end in the DNS suffix of the virtual network. Blue lines are requests for resources in the on-premises network or on the public internet.
3737

38-
![Diagram of how DNS requests are resolved in the configuration used in this document](./media/connect-on-premises-network/on-premises-to-cloud-dns.png)
38+
![Diagram of how DNS requests are resolved in the configuration](./media/connect-on-premises-network/on-premises-to-cloud-dns.png)
3939

4040
## Prerequisites
4141

@@ -92,7 +92,7 @@ These steps use the [Azure portal](https://portal.azure.com) to create an Azure
9292
|Subnet | Select the default subnet for the virtual network that you created earlier. Do __not__ select the subnet used by the VPN gateway.|
9393
|Public IP | Use the autopopulated value. |
9494

95-
![Virtual network settings](./media/connect-on-premises-network/virtual-network-settings.png)
95+
![HDInsight Virtual network settings](./media/connect-on-premises-network/virtual-network-settings.png)
9696

9797
Leave other entries at the default values and then select the **Review + create**.
9898

articles/hdinsight/domain-joined/apache-domain-joined-run-hbase.md

Lines changed: 7 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -83,15 +83,16 @@ You can use SSH to connect to HBase clusters and then use [Apache HBase Shell](h
8383
```hbaseshell
8484
scan 'Contacts'
8585
```
86-
![HDInsight Hadoop HBase shell](./media/apache-domain-joined-run-hbase/hbase-shell-scan-table.png)
86+
87+
![HDInsight Hadoop HBase shell output](./media/apache-domain-joined-run-hbase/hbase-shell-scan-table.png)
8788

8889
## Create Ranger policies
8990

9091
Create a Ranger policy for **sales_user1** and **marketing_user1**.
9192

9293
1. Open the **Ranger Admin UI**. Click **\<ClusterName>_hbase** under **HBase**.
9394

94-
![Apache Ranger Admin UI](./media/apache-domain-joined-run-hbase/apache-ranger-admin-login.png)
95+
![HDInsight Apache Ranger Admin UI](./media/apache-domain-joined-run-hbase/apache-ranger-admin-login.png)
9596

9697
2. The **List of Policies** screen will display all Ranger policies created for this cluster. One pre-configured policy may be listed. Click **Add New Policy**.
9798

@@ -197,14 +198,14 @@ Based on the Ranger policies configured, **sales_user1** can view all of the dat
197198
kinit marketing_user1
198199
```
199200

200-
2. Open the HBase shell and scan the table `Customers`:
201+
1. Open the HBase shell and scan the table `Customers`:
201202

202203
```hbaseshell
203204
hbase shell
204205
scan `Customers`
205206
```
206207

207-
3. Notice that the marketing user can only view the five columns of the `Contact` column-family.
208+
1. Notice that the marketing user can only view the five columns of the `Contact` column-family.
208209

209210
```hbaseshell
210211
ROW COLUMN+CELL
@@ -221,9 +222,9 @@ Based on the Ranger policies configured, **sales_user1** can view all of the dat
221222
2 row(s) in 0.0730 seconds
222223
```
223224

224-
9. View the audit access events from the Ranger UI.
225+
1. View the audit access events from the Ranger UI.
225226

226-
![Ranger UI Policy Audit](./media/apache-domain-joined-run-hbase/apache-ranger-admin-audit.png)
227+
![HDInsight Ranger UI Policy Audit](./media/apache-domain-joined-run-hbase/apache-ranger-admin-audit.png)
227228

228229
## Clean up resources
229230

articles/hdinsight/domain-joined/apache-domain-joined-run-kafka.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,7 @@ A [HDInsight Kafka cluster with Enterprise Security Package](./apache-domain-joi
3131

3232
2. Sign in using your Azure Active Directory (AD) admin credentials. The Azure AD admin credentials aren't the same as HDInsight cluster credentials or Linux HDInsight node SSH credentials.
3333

34-
![Apache Ranger Admin UI](./media/apache-domain-joined-run-kafka/apache-ranger-admin-login.png)
34+
![HDInsight Apache Ranger Admin UI](./media/apache-domain-joined-run-kafka/apache-ranger-admin-login.png)
3535

3636
## Create domain users
3737

@@ -178,7 +178,7 @@ Based on the Ranger policies configured, **sales_user** can produce/consume topi
178178

179179
9. View the audit access events from the Ranger UI.
180180

181-
![Ranger UI Policy Audit](./media/apache-domain-joined-run-kafka/apache-ranger-admin-audit.png)
181+
![Ranger UI policy audit access events ](./media/apache-domain-joined-run-kafka/apache-ranger-admin-audit.png)
182182

183183
## Clean up resources
184184

0 commit comments

Comments
 (0)