Skip to content

Commit aa313e1

Browse files
committed
acrolinx
1 parent d4e1df6 commit aa313e1

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

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

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ ms.date: 09/24/2018
1212

1313
# Tutorial: Configure Kafka policies in HDInsight with Enterprise Security Package
1414

15-
Learn how to configure Apache Ranger policies for Enterprise Security Package (ESP) Kafka clusters, which are connected to a domain allowing users to authenticate with domain credentials. In this tutorial, you create two Ranger policies to restrict access to `sales*` and `marketingspend` topics.
15+
Learn how to configure Apache Ranger policies for Enterprise Security Package (ESP) Kafka clusters. ESP clusters are connected to a domain allowing users to authenticate with domain credentials. In this tutorial, you create two Ranger policies to restrict access to `sales*` and `marketingspend` topics.
1616

1717
In this tutorial, you learn how to:
1818

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

159159
Example: `export KAFKAZKHOSTS=zk1-khdicl.contoso.com:2181,zk2-khdicl.contoso.com:2181`
160160

161-
4. Verifty that **sales_user1** can produce to topic **salesevents**.
161+
4. Verify that **sales_user1** can produce to topic **salesevents**.
162162

163163
Execute the following command to start the console-producer for topic **salesevents**:
164164

@@ -174,7 +174,7 @@ Based on the Ranger policies configured, **sales_user** can produce/consume topi
174174
/usr/hdp/current/kafka-broker/bin/kafka-console-consumer.sh --zookeeper $KAFKAZKHOSTS --topic salesevents --security-protocol PLAINTEXTSASL --from-beginning
175175
```
176176

177-
6. Verify that the messages you entered in the previous step will appear, and **sales_user1** cannot produce to topic **marketingspend**.
177+
6. Verify that the messages you entered in the previous step will appear, and **sales_user1** can't produce to topic **marketingspend**.
178178

179179
From the same ssh window as above, execute the following command to produce to the topic **marketingspend**:
180180

0 commit comments

Comments
 (0)