You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/purview/manage-kafka-dotnet.md
+11-11Lines changed: 11 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,7 +15,7 @@ ms.custom: mode-other
15
15
This quickstart teaches you how to send and receive *Atlas Kafka* topics events. We'll make use of *Azure Event Hubs* and the **Azure.Messaging.EventHubs** .NET library.
16
16
17
17
> [!IMPORTANT]
18
-
> A managed event hub is created automatically when your *Microsoft Purview* account is created. See, [Purview account creation](create-catalog-portal.md). You can publish messages to Event Hubs Kafka topic, ATLAS_HOOK. Purview will receive it, process it and notify Kafka topic ATLAS_ENTITIES of entity changes. This quickstart uses the new **Azure.Messaging.EventHubs** library.
18
+
> A managed event hub is created automatically when your *Microsoft Purview* account is created. See, [Microsoft Purview account creation](create-catalog-portal.md). You can publish messages to Event Hubs Kafka topic, ATLAS_HOOK. Microsoft Purview will receive it, process it and notify Kafka topic ATLAS_ENTITIES of entity changes. This quickstart uses the new **Azure.Messaging.EventHubs** library.
19
19
20
20
21
21
## Prerequisites
@@ -31,8 +31,8 @@ To follow this quickstart, you need certain prerequisites in place:
31
31
>[!NOTE]
32
32
>Enabling this Event Hubs namespace does incur a cost for the namespace. For specific details, see [the pricing page](https://azure.microsoft.com/pricing/details/purview/).
33
33
34
-
## Publish messages to Purview
35
-
Let's create a .NET Core console application that sends events to Purview via Event Hubs Kafka topic, **ATLAS_HOOK**.
34
+
## Publish messages to Microsoft Purview
35
+
Let's create a .NET Core console application that sends events to Microsoft Purview via Event Hubs Kafka topic, **ATLAS_HOOK**.
36
36
37
37
## Create a Visual Studio project
38
38
@@ -86,13 +86,13 @@ Next create a C# .NET console application in Visual Studio:
You can get the Event Hubs namespace associated with the Purview account by looking at the Atlas kafka endpoint primary/secondary connection strings. These can be found in **Properties** tab of your Purview account.
89
+
You can get the Event Hubs namespace associated with the Microsoft Purview account by looking at the Atlas kafka endpoint primary/secondary connection strings. These can be found in **Properties** tab of your account.
90
90
91
91
:::image type="content" source="media/manage-eventhub-kafka-dotnet/properties.png" alt-text="A screenshot that shows an Event Hubs Namespace.":::
92
92
93
-
The event hub name for sending messages to Purview is **ATLAS_HOOK**.
93
+
The event hub name for sending messages to Microsoft Purview is **ATLAS_HOOK**.
94
94
95
-
3. Replace the `Main` method with the following `async Main` method and add an `async ProduceMessage` to push messages into Purview. See the comments in the code for details.
95
+
3. Replace the `Main` method with the following `async Main` method and add an `async ProduceMessage` to push messages into Microsoft Purview. See the comments in the code for details.
96
96
97
97
```csharp
98
98
static async Task Main()
@@ -240,8 +240,8 @@ Next create a C# .NET console application in Visual Studio:
240
240
241
241
```
242
242
243
-
## Receive Purview messages
244
-
Next learn how to write a .NET Core console application that receives messages from event hubs using an event processor. The event processor manages persistent checkpoints and parallel receptions from event hubs. This simplifies the process of receiving events. You need to use the ATLAS_ENTITIES event hub to receive messages from Purview.
243
+
## Receive Microsoft Purview messages
244
+
Next learn how to write a .NET Core console application that receives messages from event hubs using an event processor. The event processor manages persistent checkpoints and parallel receptions from event hubs. This simplifies the process of receiving events. You need to use the ATLAS_ENTITIES event hub to receive messages from Microsoft Purview.
245
245
246
246
> [!WARNING]
247
247
> Event Hubs SDK uses the most recent version of Storage API available. That version may not necessarily be available on your Stack Hub platform. If you run this code on Azure Stack Hub, you will experience runtime errors unless you target the specific version you are using. If you're using Azure Blob Storage as a checkpoint store, review the [supported Azure Storage API version for your Azure Stack Hub build](/azure-stack/user/azure-stack-acs-differences?#api-version) and in your code, target that version.
@@ -301,11 +301,11 @@ We'll use Azure Storage as the checkpoint store. Use the following steps to crea
You can get event hub namespace associated with your Purview account by looking at your Atlas kafka endpoint primary/secondary connection strings. This can be found in the **Properties** tab of your Purview account.
304
+
You can get event hub namespace associated with your Microsoft Purview account by looking at your Atlas kafka endpoint primary/secondary connection strings. This can be found in the **Properties** tab of your Microsoft Purview account.
305
305
306
306
:::image type="content" source="media/manage-eventhub-kafka-dotnet/properties.png" alt-text="A screenshot that shows an Event Hubs Namespace.":::
307
307
308
-
Use **ATLAS_ENTITIES** as the event hub name when sending messages to Purview.
308
+
Use **ATLAS_ENTITIES** as the event hub name when sending messages to Microsoft Purview.
309
309
310
310
3. Replace the `Main` method with the following `async Main` method. See the comments in the code for details.
311
311
@@ -361,7 +361,7 @@ We'll use Azure Storage as the checkpoint store. Use the following steps to crea
361
361
> For the complete source code with more informational comments, see [this file on the GitHub](https://github.com/Azure/azure-sdk-for-net/blob/master/sdk/eventhub/Azure.Messaging.EventHubs.Processor/samples/Sample01_HelloWorld.md).
362
362
6. Run the receiver application.
363
363
364
-
### An example of a Message received from Purview
364
+
### An example of a Message received from Microsoft Purview
0 commit comments