Skip to content

Commit 04ba5d3

Browse files
committed
Fix Acrolinx issues
1 parent 0922550 commit 04ba5d3

File tree

3 files changed

+9
-9
lines changed

3 files changed

+9
-9
lines changed

articles/synapse-analytics/data-explorer/ingest-data/data-explorer-ingest-event-hub-csharp.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -45,7 +45,7 @@ In this article, you create an Event Hub data connection for Azure Synapse Data
4545

4646
## Add an Event Hub data connection
4747

48-
The following example shows you how to add an Event Hub data connection programmatically. See [connect to the event hub](data-explorer-ingest-event-hub-portal.md#connect-to-the-event-hub) for information about adding an Event Hub data connection using the Azure portal.
48+
The following example shows you how to add an Event Hub data connection programmatically. See [connect to the Event Hub](data-explorer-ingest-event-hub-portal.md#connect-to-the-event-hub) for information about adding an Event Hub data connection using the Azure portal.
4949

5050
```csharp
5151
var tenantId = "xxxxxxxx-xxxxx-xxxx-xxxx-xxxxxxxxx";//Directory (tenant) ID
@@ -68,7 +68,7 @@ var resourceGroupName = "testrg";
6868
var clusterName = "mykustocluster";
6969
var databaseName = "mykustodatabase";
7070
var dataConnectionName = "myeventhubconnect";
71-
//The event hub that is created as part of the Prerequisites
71+
//The Event Hub that is created as part of the Prerequisites
7272
var eventHubResourceId = "/subscriptions/xxxxxxxx-xxxxx-xxxx-xxxx-xxxxxxxxx/resourceGroups/xxxxxx/providers/Microsoft.EventHub/namespaces/xxxxxx/eventhubs/xxxxxx";
7373
var consumerGroup = "$Default";
7474
var location = "Central US";
@@ -101,7 +101,7 @@ await kustoManagementClient.DataConnections.CreateOrUpdateAsync(resourceGroupNam
101101

102102
## Generate data
103103

104-
See the [sample app](https://github.com/Azure-Samples/event-hubs-dotnet-ingest) that generates data and sends it to an event hub.
104+
See the [sample app](https://github.com/Azure-Samples/event-hubs-dotnet-ingest) that generates data and sends it to an Event Hub.
105105

106106
An event can contain one or more records, up to its size limit. In the following sample we send two events, each has five records appended:
107107

articles/synapse-analytics/data-explorer/ingest-data/data-explorer-ingest-event-hub-overview.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -51,7 +51,7 @@ Ingestion properties instruct the ingestion process, where to route the data, an
5151
When you set up an Event Hub connection to Azure Synapse Data Explorer cluster, you specify target table properties (table name, data format, compression, and mapping). The default routing for your data is also referred to as `static routing`.
5252
You can also specify target table properties for each event, using event properties. The connection will dynamically route the data as specified in the [EventData.Properties](/dotnet/api/microsoft.servicebus.messaging.eventdata.properties#Microsoft_ServiceBus_Messaging_EventData_Properties), overriding the static properties for this event.
5353

54-
In the following example, set event hub details and send weather metric data to table `WeatherMetrics`.
54+
In the following example, set Event Hub details and send weather metric data to table `WeatherMetrics`.
5555
Data is in `json` format. `mapping1` is pre-defined on the table `WeatherMetrics`.
5656

5757
```csharp
@@ -106,15 +106,15 @@ If you selected **Event system properties** in the **Data Source** section of th
106106
107107
### Create an Event Hub
108108

109-
If you don't already have one, [Create an event hub](/azure/event-hubs/event-hubs-create). Connecting to Event Hub can be managed through the [Azure portal](data-explorer-ingest-event-hub-portal.md), programmatically with [C#](data-explorer-ingest-event-hub-csharp.md) or [Python](data-explorer-ingest-event-hub-python.md), or with the [Azure Resource Manager template](data-explorer-ingest-event-hub-resource-manager.md).
109+
If you don't already have one, [Create an Event Hub](/azure/event-hubs/event-hubs-create). Connecting to Event Hub can be managed through the [Azure portal](data-explorer-ingest-event-hub-portal.md), programmatically with [C#](data-explorer-ingest-event-hub-csharp.md) or [Python](data-explorer-ingest-event-hub-python.md), or with the [Azure Resource Manager template](data-explorer-ingest-event-hub-resource-manager.md).
110110

111111
> [!Note]
112112
> * The partition count isn't changeable, so you should consider long-term scale when setting partition count.
113113
> * Consumer group *must* be unique per consumer. Create a consumer group dedicated to Azure Synapse Data Explorer connection.
114114
115115
## Send events
116116

117-
See the [sample app](https://github.com/Azure-Samples/event-hubs-dotnet-ingest) that generates data and sends it to an event hub.
117+
See the [sample app](https://github.com/Azure-Samples/event-hubs-dotnet-ingest) that generates data and sends it to an Event Hub.
118118

119119
For an example of how to generate sample data, see [Ingest data from Event Hub into Azure Synapse Data Explorer](data-explorer-ingest-event-hub-portal.md#generate-sample-data)
120120

articles/synapse-analytics/data-explorer/ingest-data/data-explorer-ingest-event-hub-portal.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -84,15 +84,15 @@ Create an Event Hub by using an Azure Resource Manager template in the Azure por
8484
| Resource group | *test-hub-rg* | Create a new resource group. |
8585
| Location | *West US* | Select *West US* for this article. For a production system, select the region that best meets your needs. Create the Event Hub namespace in the same Location as the Azure Synapse Data Explorer cluster for best performance (most important for Event Hub namespaces with high throughput).
8686
| Namespace name | A unique namespace name | Choose a unique name that identifies your namespace. For example, *mytestnamespace*. The domain name *servicebus.windows.net* is appended to the name you provide. The name can contain only letters, numbers, and hyphens. The name must start with a letter, and it must end with a letter or number. The value must be between 6 and 50 characters long.
87-
| Event hub name | *test-hub* | The Event Hub sits under the namespace, which provides a unique scoping container. The Event Hub name must be unique within the namespace. |
87+
| Event Hub name | *test-hub* | The Event Hub sits under the namespace, which provides a unique scoping container. The Event Hub name must be unique within the namespace. |
8888
| Consumer group name | *test-group* | Consumer groups enable multiple consuming applications to each have a separate view of the event stream. |
8989
| | |
9090
9191
1. Select **Review + create**.
9292
9393
1. Review the **Summary** of resources created. Select **Create**, which acknowledges that you're creating resources in your subscription.
9494
95-
:::image type="content" source="../media/ingest-data-event-hub/review-create.png" alt-text="Screen shot of Azure portal for reviewing and creating EventHubs namespace, Event Hub, and consumer group.":::
95+
:::image type="content" source="../media/ingest-data-event-hub/review-create.png" alt-text="Screen shot of Azure portal for reviewing and creating Event Hub namespace, Event Hub, and consumer group.":::
9696
9797
1. Select **Notifications** on the toolbar to monitor the provisioning process. It might take several minutes for the deployment to succeed, but you can move on to the next step now.
9898
@@ -206,7 +206,7 @@ With the app generating data, you can now see the flow of that data from the Eve
206206
207207
1. In the Azure portal, under your Event Hub, you see the spike in activity while the app is running.
208208
209-
![Event hub graph.](../media/ingest-data-event-hub/event-hub-graph.png)
209+
![Event Hub graph.](../media/ingest-data-event-hub/event-hub-graph.png)
210210
211211
1. To check how many messages have made it to the database so far, run the following query in your test database.
212212

0 commit comments

Comments
 (0)