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/synapse-analytics/data-explorer/ingest-data/data-explorer-ingest-event-hub-csharp.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -45,7 +45,7 @@ In this article, you create an Event Hub data connection for Azure Synapse Data
45
45
46
46
## Add an Event Hub data connection
47
47
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.
49
49
50
50
```csharp
51
51
vartenantId="xxxxxxxx-xxxxx-xxxx-xxxx-xxxxxxxxx";//Directory (tenant) ID
@@ -68,7 +68,7 @@ var resourceGroupName = "testrg";
68
68
varclusterName="mykustocluster";
69
69
vardatabaseName="mykustodatabase";
70
70
vardataConnectionName="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
Copy file name to clipboardExpand all lines: articles/synapse-analytics/data-explorer/ingest-data/data-explorer-ingest-event-hub-overview.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -51,7 +51,7 @@ Ingestion properties instruct the ingestion process, where to route the data, an
51
51
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`.
52
52
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.
53
53
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`.
55
55
Data is in `json` format. `mapping1` is pre-defined on the table `WeatherMetrics`.
56
56
57
57
```csharp
@@ -106,15 +106,15 @@ If you selected **Event system properties** in the **Data Source** section of th
106
106
107
107
### Create an Event Hub
108
108
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).
110
110
111
111
> [!Note]
112
112
> * The partition count isn't changeable, so you should consider long-term scale when setting partition count.
113
113
> * Consumer group *must* be unique per consumer. Create a consumer group dedicated to Azure Synapse Data Explorer connection.
114
114
115
115
## Send events
116
116
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.
118
118
119
119
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)
Copy file name to clipboardExpand all lines: articles/synapse-analytics/data-explorer/ingest-data/data-explorer-ingest-event-hub-portal.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -84,15 +84,15 @@ Create an Event Hub by using an Azure Resource Manager template in the Azure por
84
84
| Resource group | *test-hub-rg* | Create a new resource group. |
85
85
| 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).
86
86
| 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. |
88
88
| Consumer group name | *test-group* | Consumer groups enable multiple consuming applications to each have a separate view of the event stream. |
89
89
| | |
90
90
91
91
1. Select **Review + create**.
92
92
93
93
1. Review the **Summary** of resources created. Select **Create**, which acknowledges that you're creating resources in your subscription.
94
94
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.":::
96
96
97
97
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.
98
98
@@ -206,7 +206,7 @@ With the app generating data, you can now see the flow of that data from the Eve
206
206
207
207
1. In the Azure portal, under your Event Hub, you see the spike in activity while the app is running.
0 commit comments